pip-check-reqs 2.1.1-3 source package in Ubuntu
Changelog
pip-check-reqs (2.1.1-3) unstable; urgency=medium * Bump Standards-Version up to 4.5.1. * Run `wrap-and-sort -ast`. * Bump copyright year in debian/copyright. * Add upstream metadata file. -- Francois Marier <email address hidden> Mon, 18 Jan 2021 23:20:05 -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 |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
pip-check-reqs_2.1.1-3.dsc | 2.1 KiB | 8d77a695eccf22cd8c2745bbb499b8bed120451429ee3285ed7539ac45fc2511 |
pip-check-reqs_2.1.1.orig.tar.gz | 9.8 KiB | 469f268fc06d32e5bcedb777c2b800d2586496ca5de2d181f02ffeda6f15be45 |
pip-check-reqs_2.1.1-3.debian.tar.xz | 3.4 KiB | 85f556297b624244cdc99c5649e0612f7a5f382e52c3e041d53dae5efd3a8f65 |
Available diffs
- diff from 2.1.1-2 to 2.1.1-3 (990 bytes)
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.