Setuptools continuous integration command
This package adds continuous integration tools for setup.py.
It will install :
nose for unit testing
nosexcover for code coverage
setuptools-clonedigger for detecting similar code
setuptools-flakes for analyze and detect various errors
setuptools-lint for code quality
setuptools-sloccount for counting physical source lines of code
Usage
python setup.py ci
Will execute all commands. See each command documentation for configuration.
And voilà!
News
0.1
Release date: 6-Jun-2012
First release
1 maintainer
Metadata
1 maintainer
Release files for setuptools-ci 0.1
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-ci-0.1.tar.gz | 2.4 kB | Without provenance | Details |
Release files / setuptools-ci-0.1.tar.gz
| Download URL | setuptools-ci-0.1.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb6f9d854043016983ef2d83f86f56c9040582b4b687704eec904aaba72080a1
|
|
BLAKE2b-256 checksum How to use checksums |
8457a177f0cd859959ab65b3136c60801c1c99f338b79c8cb7102fd047d450ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for setuptools-ci 0.1
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.
