Skip to main content

Find packages that should be in requirements for a project

Project description

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. This tool finds those modules so you can include them in the requirements.txt for the project.

Assuming your project follows a layout like the suggested sample project:

setup.py
setup.cfg
requirements.txt
sample/__init__.py
sample/sample.py
sample/tests/test_sample.py

Basic usage, running in your project directory:

<activate virtualenv for your project>
pip-missing-reqs --ignore-file=sample/tests/* sample

This will find all imports in the code in “sample” and check that the packages those modules belong to are in the requirements.txt file.

Sample tox.ini configuration

To make your life easier, copy something like this into your tox.ini:

[testenv:pip-missing-reqs]
deps=-rrequirements.txt
commands=pip-missing-reqs --ignore-file=sample/tests/* sample

Excluding test files (or others) from this check

Your test files will sometimes be present in the same directory as your application source (“sample” in the above examples). The requirements for those tests generally should not be in the requirements.txt file, and you don’t want this tool to generate false hits for those.

You may exclude those test files from your check using the –ignore-file option (shorthand is -f). Multiple instances of the option are allowed.

Excluding modules from the check

If your project has modules which are conditionally imported, or requirements which are conditionally included, you may exclude certain modules from the check by name (or glob pattern) using –ignore-module (shorthand is -m):

# ignore the module spam
pip-missing-reqs --ignore-module=spam sample
# ignore the whole package spam as well
pip-missing-reqs --ignore-module=spam --ignore-module=spam.* sample

Release History

1.2.0

  • bumped pip requirement to 6.0.8+

  • updated use of pip internals to match that version

1.1.9

  • test fixes and cleanup

  • remove hard-coded simplejson debugging behaviour

1.1.8

  • use os.path.realpath to avoid symlink craziness on debian/ubuntu

1.1.7

  • tweak to debug output

1.1.6

  • add debug (very verbose) run output

1.1.5

  • add header to output to make it clearer when in a larger test run

  • fix tests and self-test

1.1.4

  • add –version

  • remove debug print from released code lol

1.1.3

  • fix program to generate exit code useful for testing

1.1.2

  • corrected version of vendored search_packages_info() from pip

  • handle relative imports

1.1.1

  • fixed handling of import from __future__

  • self-tested and added own requirements.txt

  • cleaned up usage to require a file or directory to scan (rather than defaulting to “.”)

  • vendored code from pip 1.6dev which fixes bug in search_packages_info until pip 1.6 is released

1.1.0

  • implemented –ignore-module

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pip_missing_reqs-1.2.0.tar.gz (8.9 kB view details)

Uploaded Source

File details

Details for the file pip_missing_reqs-1.2.0.tar.gz.

File metadata

File hashes

Hashes for pip_missing_reqs-1.2.0.tar.gz
Algorithm Hash digest
SHA256 4dca2f4832bc5b09919d63dffee522cb33fef7ce61b94f6210b65fa03b862a9c
MD5 4a4a568fa1d09a97ed009d79761f67f1
BLAKE2b-256 ed4a4ff4fb296cf1942177a4296a0ff551bc17d260e88504193e25d93d6833c1

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page