pip-check-reqs 2.4.3-1 source package in Ubuntu
Changelog
pip-check-reqs (2.4.3-1) unstable; urgency=medium * New upstream release * Bump Standards-Version up to 4.6.2. * Bump copyright years in debian/copyright and fix upstream contact name. -- Francois Marier <email address hidden> Mon, 02 Jan 2023 13:25:38 -0800
Upload details
- Uploaded by:
- François Marier
- Uploaded to:
- Sid
- Original maintainer:
- François Marier
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Mantic | release | universe | misc | |
| Lunar | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| pip-check-reqs_2.4.3-1.dsc | 2.1 KiB | e2195d22a5276d1e592bb882f9932ffc7a0f75e9001fb4d101315bffdedaa002 |
| pip-check-reqs_2.4.3.orig.tar.gz | 14.1 KiB | 1b6f5dbde109a2a746c50650d6eebfa61359718f35691cae48802e4a7d7da549 |
| pip-check-reqs_2.4.3-1.debian.tar.xz | 3.5 KiB | cb0980f73d3537b0f8fcc00d1f1228bc8f616eb333d7d77f7816f67ba3170e6c |
Available diffs
- diff from 2.4.2-1 to 2.4.3-1 (10.2 KiB)
No changes file available.
Binary packages built by this source
- pip-check-reqs: checker for missing and extra packages in Python requirements
It happens: you start using a module in your project and it works and you
don't realise that it's only being included in your virtualenv because it's
a dependency of a package you're using. pip-missing-reqs finds those modules
so you can include them in the requirements.txt for the project.
.
Alternatively, you have a long-running project that has some packages in
requirements.txt that are no longer actively used in the codebase. The
pip-extra-reqs tool will find those modules so you can remove them.
