|
3 | 3 | Code Style
|
4 | 4 | ==========
|
5 | 5 |
|
6 |
| -If you ask Python programmers what they like most in Python, they will |
7 |
| -often say its high readability. Indeed, a high level of readability |
| 6 | +If you ask Python programmers what they like most about Python, they will |
| 7 | +often cite its high readability. Indeed, a high level of readability |
8 | 8 | is at the heart of the design of the Python language, following the
|
9 | 9 | recognized fact that code is read much more often than it is written.
|
10 | 10 |
|
11 |
| -One reason for Python code to be easily read and understood is its relatively |
| 11 | +One reason for the high readability of Python code is its relatively |
12 | 12 | complete set of Code Style guidelines and "Pythonic" idioms.
|
13 | 13 |
|
14 |
| -Moreover, when a veteran Python developer (a Pythonista) points to portions of |
15 |
| -code and says they are not "Pythonic", it usually means that these lines |
16 |
| -of code do not follow the common guidelines and fail to express the intent in |
| 14 | +When a veteran Python developer (a Pythonista) calls portions of |
| 15 | +code not "Pythonic", they usually mean that these lines |
| 16 | +of code do not follow the common guidelines and fail to express its intent in |
17 | 17 | what is considered the best (hear: most readable) way.
|
18 | 18 |
|
19 | 19 | On some border cases, no best way has been agreed upon on how to express
|
@@ -53,7 +53,7 @@ One statement per line
|
53 | 53 |
|
54 | 54 | While some compound statements such as list comprehensions are
|
55 | 55 | allowed and appreciated for their brevity and their expressiveness,
|
56 |
| -it is bad practice to have two disjoint statements on the same line of code. |
| 56 | +it is bad practice to have two disjointed statements on the same line of code. |
57 | 57 |
|
58 | 58 | **Bad**
|
59 | 59 |
|
|
0 commit comments