pip_missing_reqs 1.1.4

Sample tox.ini configuration

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

[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.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