Setuptools pep8 command
Originally based on https://github.com/johnnoone/setuptools-pylint
This package exposes the pep8 style guide checker as a sub-command of setup.py:
$ cat setup.py
...
setup(
name='your project',
setup_requires=['setuptools-pep8']
)
....
$ cat setup.cfg
...
[pep8]
ignore=E225
...
$ python setup.py pep8
running pep8
./setup.py:41:1: W391 blank line at end of file
This invokes pep8 and applies any configuration from your setup.cfg file’s [pep8] section. Typical use cases include simplification of continuous-integration job configurations.
News
0.9.0
Release date: 29-Dec-2013
Final major release before v1.0 (project goes into maint mode).
Contains non-backwards-compatable changes!
Bugfixes:
Resolves clash with setuptools Command –verbose flag
Features:
All pep8 cmdline options can now be specified on the python setup.py pep8 command line
pep8 return code is propagated to the python setup.py command return code
Non-Functional Changes:
Drastic simplification of pep8 setuptools Command implementation
Minor changes to testing code (adopt usage of process return code)
Backwards Incompatable Changes:
–pep8-output option has been removed. Replace usage of this with shell redirection.
–check-dirs option has been removed. Replace usage of this with pep8’s –exclude option.
Any users wishing to retain these features are advised to stay on version 0.2.0.
0.2.0
Release date: 28-Dec-2013
Stable build, promoted minor version. No functional changes.
0.1.7
Release date: 28-Dec-2013
Enabled Travis-CI integration testing
Configured auto upload from Travis -> PyPI for tagged releases
Minor formatting tweaks
0.1.6
Release date: Not released
Minor tweak to .rst syntax, fix rendering issues on PyPI
0.1.5
Release date: 3-Dec-2013
Bugfix: missing NEWS.rst in manifest
0.1.4
Release date: 3-Dec-2013
@yoloseem fixed indentation bug
Fixed setup.cfg parsing of include / exclude directives
0.1.3
Release date: 6-Oct-2013
Fixed github issue #1: Setting pep8 directives in setup.cfg doesn’t work
Exposed –check-dirs= option to control which modules are checked
Fixed incorrect handling of stdout/stderr when redirecting pep8 output to a file
0.1.2
Release date: 4-Oct-2013
Adds in config parsing from setup.cfg
Semantic versioning
1 maintainer
Metadata
1 maintainer
Release files for setuptools-pep8 0.9.0
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 | |
|---|---|---|---|---|
| setuptools-pep8-0.9.0.tar.gz | 4.1 kB | Without provenance | Details |
Release files / setuptools-pep8-0.9.0.tar.gz
| Download URL | setuptools-pep8-0.9.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f620cd7494015729249bda7260c9b94900d6e6ab27df46051fb144c32627080c
|
|
BLAKE2b-256 checksum How to use checksums |
208af75f0126e3809a98b8bd850b93389b35f04958653c3bb5d1b2de5f33c349
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for setuptools-pep8 0.9.0
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.
