Skip to content

PEP 8 Explicitly State Variable Names convention? #535 #545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
warsaw merged 2 commits into from
Jan 17, 2018
Merged

PEP 8 Explicitly State Variable Names convention? #535 #545

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8d314c
Update pep-0008.txt
Carl-ty Jan 17, 2018
9d9d593
Update pep-0008.txt
Carl-ty Jan 17, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions pep-0008.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -914,12 +914,14 @@ older convention of prefixing such globals with an underscore (which
you might want to do to indicate these globals are "module
non-public").

Function Names
~~~~~~~~~~~~~~
Function and variable names
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Function names should be lowercase, with words separated by
underscores as necessary to improve readability.

Variable names follow the same convention as function names.

mixedCase is allowed only in contexts where that's already the
prevailing style (e.g. threading.py), to retain backwards
compatibility.
Expand Down