Tweak source encoding wording
This commit is contained in:
parent
05d72183a8
commit
5dbb9a10f1
|
@ -244,14 +244,15 @@ you may use them to separate pages of related sections of your file.
|
||||||
Note, some editors and web-based code viewers may not recognize
|
Note, some editors and web-based code viewers may not recognize
|
||||||
control-L as a form feed and will show another glyph in its place.
|
control-L as a form feed and will show another glyph in its place.
|
||||||
|
|
||||||
Encodings (PEP 263)
|
|
||||||
-------------------
|
Source File Encoding
|
||||||
|
--------------------
|
||||||
|
|
||||||
Code in the core Python distribution should always use UTF-8 (or ASCII
|
Code in the core Python distribution should always use UTF-8 (or ASCII
|
||||||
in Python 2).
|
in Python 2).
|
||||||
|
|
||||||
Files using ASCII (in Python 2) or UTF-8 (in Python 3) should not have a
|
Files using ASCII (in Python 2) or UTF-8 (in Python 3) should not have
|
||||||
coding cookie.
|
an encoding declaration.
|
||||||
|
|
||||||
In the standard library, non-default encodings should be used only for
|
In the standard library, non-default encodings should be used only for
|
||||||
test purposes or when a comment or docstring needs to mention an author
|
test purposes or when a comment or docstring needs to mention an author
|
||||||
|
|
Loading…
Reference in New Issue