Check for differences between requirements.txt files and the current environment.
Working on a Django project? Check out my book Boost Your Django DX which covers many ways to improve your development experience.
Installation
Install with python -m pip install pip-lock.
Python 3.9 to 3.14 supported.
Example usage
Call pip_lock.check_requirements() at your application startup to verify that the current virtual environment matches your requirements file. This gives instant feedback to developers changing branches etc. who would otherwise experience unexpected behaviour or errors due to out of sync requirements.
In a Django project, it makes sense to add the check inside the manage.py file, which is the project’s main entrypoint. You can add a call to pip_lock.check_requirements() after the first import of Django. For example:
#!/usr/bin/env python
import os
import sys
from pathlib import Path
def main():
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "example.settings")
try:
from django.core.management import execute_from_command_line
except ImportError as exc:
raise ImportError(
"Couldn't import Django. Are you sure it's installed and "
"available on your PYTHONPATH environment variable? Did you "
"forget to activate a virtual environment?"
) from exc
try:
import pip_lock
except ImportError:
raise ImportError(
"Couldn't import pip-lock. Are you on the right virtualenv and up "
+ "to date?"
)
requirements_path = str(Path(__file__).parent / "requirements.txt")
pip_lock.check_requirements(
requirements_path,
post_text="\nRun the following:\n\npython -m pip install -r requirements.txt\n",
)
execute_from_command_line(sys.argv)
if __name__ == "__main__":
main()API
check_requirements(requirements_file_path: str, post_text: str='') -> None
Exit with exit code 1 and output to stderr if there are mismatches between the environment and requirements file.
requirements_file_path is the path to the requirements.txt file - we recommend using an absolute file path.
post_text is optional text which is displayed after the stderr message. This can be used to display instructions on how to update the requirements.
Example:
check_requirements(
"requirements.txt",
post_text="\nRun the following on your host machine: \n\n vagrant provision\n",
)There are requirement mismatches with requirements.txt:
* Package Django has version 1.9.10 but you have version 1.9.0 installed.
* Package requests has version 2.11.1 but you have version 2.11.0 installed.
* Package requests-oauthlib is in requirements.txt but not in virtualenv
Run the following on your host machine:
vagrant provisionget_mismatches(requirements_file_path: str) -> dict[str, tuple[str, str | None]]
Return a dictionary of package names to tuples of (expected_version, actual_version) for mismatched packages.
requirements_file_path is the path to the requirements.txt file - we recommend using an absolute file path.
Example:
>>> get_mismatches("requirements.txt")
{'django': ('1.10.2', '1.9.0'), 'requests': ('2.11.1', '2.9.2'), 'request-oauthlib': ('0.7.0', None)}3 maintainers
Release files for pip-lock 2.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pip_lock-2.13.0.tar.gz | 7.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pip_lock-2.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / pip_lock-2.13.0.tar.gz
| Download URL | pip_lock-2.13.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c51bf7e696c1e029fde47b63a9272186ae2515954964e8cd12dddff1e87f706
|
|
BLAKE2b-256 checksum How to use checksums |
e1bd94abe7b50bea71d09befa743dfe04fdf155db48219af784fea18e89415a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2025.
Transparency logRelease files / pip_lock-2.13.0-py3-none-any.whl
| Download URL | pip_lock-2.13.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a48d4e08ab6d6779b5f5af3d71183f05b5c528e3acdaaf93d1af1c5012f7dbed
|
|
BLAKE2b-256 checksum How to use checksums |
556f26b227fc45ac915b5210e63e0b483e4892db1a9d0e95fa13851f8261f5f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2025.
Transparency log
