Andreas/evennia
1
0
Fork 0
mirror of https://github.com/evennia/evennia.git synced 2026-03-16 21:06:30 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #2558 from dimitrilw/dev-docs-no-reuse-BIFs

Browse source 
Dev docs no reuse BIFs
This commit is contained in:
Griatch 2021-10-12 19:17:39 +02:00 • committed by GitHub
commit ae2369a17b
2 changed files with 5 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
.gitignore vendored
View file

@ -53,3 +53,6 @@ docs/build
# For users of Atom
.remote-sync.json
# Visual Studio Code (VS-Code)
.vscode/

4
docs/source/Howto/Starting/Part1/Python-basic-introduction.md
View file

@ -128,7 +128,7 @@ instead.
Here's the stat-example again, moving the stats to variables (here we just set them, but in a real
game they may be changed over time, or modified by circumstance):
> py str, dex, int = 13, 14, 8 ; print("STR: {}, DEX: {}, INT: {}".format(stren, dex, int))
> py stren, dex, intel = 13, 14, 8 ; print("STR: {}, DEX: {dex}, INT: {}".format(stren, dex, intel))
STR: 13, DEX: 14, INT: 8
The point is that even if the values of the stats change, the print() statement would not change - it just keeps
@ -148,7 +148,7 @@ An f-string on its own is just like any other string. But let's redo the example
We could just insert that `a` variable directly into the f-string using `{a}`. Fewer parentheses to
remember and arguable easier to read as well.
> py str, dex, int = 13, 14, 8 ; print(f"STR: {str}, DEX: {dex}, INT: {int}")
> py stren, dex, intel = 13, 14, 8 ; print(f"STR: {stren}, DEX: {dex}, INT: {intel}")
STR: 13, DEX: 14, INT: 8
We will be exploring more complex string concepts when we get to creating Commands and need to