iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 8: Fix typos (#2600)

This commit is contained in:
jbritton6 2022-05-11 13:45:05 -04:00 committed by GitHub
parent a45a339549
commit 46efeee6d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0008.txt
View File

@ -296,7 +296,7 @@ related one-liners (e.g. a set of dummy implementations).
Use blank lines in functions, sparingly, to indicate logical sections.
Python accepts the control-L (i.e. ^L) form feed character as
whitespace; Many tools treat these characters as page separators, so
whitespace; many tools treat these characters as page separators, so
you may use them to separate pages of related sections of your file.
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.
@ -1359,7 +1359,7 @@ Function Annotations
With the acceptance of :pep:`484`, the style rules for function
annotations have changed.
- Function annotations should use :pep:`484` syntax (There are some
- Function annotations should use :pep:`484` syntax (there are some
formatting recommendations for annotations in the previous section).
- The experimentation with annotation styles that was recommended