pip-check-reqs 2.4.2-1 source package in Ubuntu
Changelog
pip-check-reqs (2.4.2-1) unstable; urgency=medium * New upstream release * Bump Standards-Version up to 4.6.1. * Bump copyright years in debian/copyright. -- Francois Marier <email address hidden> Wed, 02 Nov 2022 22:37:38 -0700
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 |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
pip-check-reqs_2.4.2-1.dsc | 2.1 KiB | 7df608a0188721c1c098d54a36f62d84563d7b6172086ac177840540c24add5c |
pip-check-reqs_2.4.2.orig.tar.gz | 12.2 KiB | 6fdd0e25d431b88168c20116cd870c746c6cbe35567b04d8e4da919c96369088 |
pip-check-reqs_2.4.2-1.debian.tar.xz | 3.5 KiB | ec8f71de6ef27c96cc1bf6bf80900e33787d0c32940e556144c66b6841682ba3 |
Available diffs
- diff from 2.3.2-1 to 2.4.2-1 (8.3 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.