Parents (Total: 2)
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key |
Value |
FileSize | 12780 |
MD5 | B4E019E99E191209CE27293837182C73 |
PackageDescription | 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. |
PackageMaintainer | Francois Marier <francois@debian.org> |
PackageName | pip-check-reqs |
PackageSection | devel |
PackageVersion | 2.1.1-3 |
SHA-1 | 70AA3D019D975590C824D23D60535FA58D8614C9 |
SHA-256 | FE5C90ACE39504F4C25A638CACB59104125232093B0CCA7A6F020F189C4D31C7 |
Key |
Value |
FileSize | 11836 |
MD5 | B0A224F5B9EB7B43C0FF0E10921AD7CB |
PackageDescription | 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. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | pip-check-reqs |
PackageSection | devel |
PackageVersion | 2.1.1-3 |
SHA-1 | 0214A5B0D30B7B0403A497DFF87B60BDB7924329 |
SHA-256 | D09334CA46618E5884724083AB79864AD4EB4122BA09CBD17861EC1ACC735D19 |