PEP-8 Naming Conventions
Check the PEP-8 naming conventions.
This module provides a plugin for flake8, the Python code checker.
(It replaces the plugin flint-naming for the flint checker.)
Installation
You can install, upgrade, uninstall pep8-naming with these commands:
$ pip install pep8-naming $ pip install --upgrade pep8-naming $ pip uninstall pep8-naming
Plugin for Flake8
When both flake8 and pep8-naming are installed, the plugin is available in flake8:
$ flake8 --version 2.0 (pep8: 1.4.3, pyflakes: 0.6.1, naming: 0.2)
By default the plugin is enabled.
These error codes are emitted:
code |
sample message |
|---|---|
N801 |
class names should use CapWords convention |
N802 |
function name should be lowercase |
N803 |
argument name should be lowercase |
N804 |
first argument of a classmethod should be named ‘cls’ |
N805 |
first argument of a method should be named ‘self’ |
N806 |
variable in function should be lowercase |
N811 |
constant imported as non constant |
N812 |
lowercase imported as non lowercase |
N813 |
camelcase imported as lowercase |
N814 |
camelcase imported as constant |
Changes
0.3.3 - 2015-06-30
Fix bug where ignored names were not properly split into a list.
0.3.2 - 2015-06-14
Fix bug trying to call split on a list.
0.3.1 - 2015-06-14
Fix optparse exception resulting from trying to register an option twice.
0.3.0 - 2015-06-14
Relaxed N806 checking for use with namedtuples
Add --ignore-names which allows the user to specify a list of names to ignore. By default this includes setUp, tearDown, setUpClass, and tearDownClass.
0.2.2 - 2014-04-19
Do not require setuptools in setup.py. It works around an issue with pip and Python 3.
__new__ is now considered as classmethod implicitly
Run unit tests on travis-ci.org for python2.6, 2.7, 3.2, and 3.3
Add unit tests and support running them with setup.py
Support Python 3.4
0.2.1 - 2013-02-22
Do not require flake8
0.2 - 2013-02-22
Rename project flint-naming to pep8-naming
Fix a crash when function argument is a tuple of tuples
0.1 - 2013-02-11
First release
Release files for pep8-naming 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pep8-naming-0.3.3.tar.gz | 5.8 kB | Without provenance | Details for pep8-naming-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pep8_naming-0.3.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for pep8_naming-0.3.3-py2.py3-none-any.whl |
Total release size: 13.6 kB
Release files / pep8-naming-0.3.3.tar.gz
| Download URL | pep8-naming-0.3.3.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc691c3f9a6022a41be0787c66cf269b415af07f151c682a946016928106f67e
|
|
BLAKE2b-256 checksum How to use checksums |
5a8e0378581bef6e99f111d1f591d3f9f52625f75148119d49546b33f43aab40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pep8_naming-0.3.3-py2.py3-none-any.whl
| Download URL | pep8_naming-0.3.3-py2.py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7b45331e92b78f87787936084270369015a4d932bc80eabcc6316de29955d52c
|
|
BLAKE2b-256 checksum How to use checksums |
a88595d867875ccecc068511c704872c420edbba654a21e78927b806a8d67b89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pep8-naming 0.3.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
