Extra distutils commands, including:
clean_pyc: clean compiled python files
clean_all: using distutils.clean and clean_pyc to clean all temporary files
bdist_pyinstaller: convenient calls for PyInstaller with sane defaults
test: run unit tests
How
Make sure distutilazy package is in sys.path, then add distutilazy.command package to the list of command packages in your setup.cfg file.
[global] command_packages = distutilazy.command
That’s it. now you may use new commands directly from your setup.py:
To clean compiled python files from the project:
$ python setup.py clean_pycTo run unit tests (by default runs tests/test*.py files):
$ python setup.py testAvailable commands are in distutilazy.command package as separate modules.
A more detailed way is to use command classes, defined in distutilazy package modules. Each module might define more than a single command class.
The modules should be imported in setup.py, then desired classes might be assigned to command names using the cmdclass parameter.
import distutilazy.clean
setup(
cmdclass: {'clean_pyc': distutilazy.clean.clean_pyc}
)
License
Distutilazy is released under the terms of MIT license.
1 maintainer
Metadata
1 maintainer
Release files for distutilazy 0.3.2
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 |
|---|---|---|---|---|
| distutilazy-0.3.2.tar.gz | 10.6 kB | Without provenance | Details for distutilazy-0.3.2.tar.gz |
Release files / distutilazy-0.3.2.tar.gz
| Download URL | distutilazy-0.3.2.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29029d161531fcb03228b7dfc96388e1d20e44bca40093b895d5008140bda681
|
|
BLAKE2b-256 checksum How to use checksums |
67fd37c83031895e1059903733b092916b683d3785d8795898a109446123b5d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for distutilazy 0.3.2
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.
