pip-check-reqs 2.5.3-1 source package in Ubuntu

Changelog

pip-check-reqs (2.5.3-1) unstable; urgency=medium

  * New upstream release
    This was released on PyPI as 2.5.3, but is listed on GitHub as 2.5.2.
    See https://github.com/r1chardj0n3s/pip-check-reqs/issues/163.

 -- Francois Marier <email address hidden>  Sat, 16 Sep 2023 11:53:12 -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 Pocket Published Component Section
Questing release universe misc
Plucky release universe misc
Oracular release universe misc
Noble release universe misc

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
pip-check-reqs_2.5.3-1.dsc 2.1 KiB a1ebf1da4bf1d9a251d3be2cc4b611a764d9da33e9fe86127897b8ee56f3ab02
pip-check-reqs_2.5.3.orig.tar.gz 19.1 KiB 0b7ef9dfd6efc691164d991c961047dbd74a8609e2eb3e33c09b58f85d6cfa09
pip-check-reqs_2.5.3-1.debian.tar.xz 3.6 KiB 314e11a893b8c2bbbbb62fcf7a5d1db97b2fba64f67122ee9fc67a927e60b2f8

Available diffs

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.