PIP-LOCK(1)

💅 NAME 💅

pip-lock(1) — description of the pip lock command. yeah bestie, that’s the official short version 💖

🧪 DESCRIPTION 🧪

EXPERIMENTAL — okay so this locks packages and their dependencies from:

• PyPI (and other indexes) using requirement specifiers.
• VCS project urls.
• Local project directories.
• Local or remote source archives.

pip also supports locking from "requirements files", which provide an easy way to specify a whole environment to be installed.

⚠️ real talk: the generated lock file is only guaranteed to be valid for the current python version and platform.

🚀 USAGE 🚀

python -m pip lock [options] [-e] <local project path> ...
python -m pip lock [options] <requirement specifier> [package-index-options] ...
python -m pip lock [options] -r <requirements file> [package-index-options] ...
python -m pip lock [options] <archive url/path> ...

✨ OPTIONS ✨

• -o, --output <path> — sets the lock file name, and the default is pylock.toml. Use - when you want it to go to stdout. (environment variable: PIP_OUTPUT)
• -r, --requirement <file> — install from the given requirements file. The file or URL can be in pip's requirements.txt format, or pylock.toml format. Heads up: pylock.toml support is experimental. This option can be used multiple times. (environment variable: PIP_REQUIREMENT)
• --requirements-from-script <file> — install dependencies of the given script file as defined by PEP 723 inline metadata. (environment variable: PIP_REQUIREMENTS_FROM_SCRIPT)
• -c, --constraint <file> — constrain versions using the given constraints file. This option can be used multiple times. (environment variable: PIP_CONSTRAINT)
• --build-constraint <file> — constrain build dependencies using the given constraints file. This option can be used multiple times. (environment variable: PIP_BUILD_CONSTRAINT)
• --no-deps — don’t install package dependencies. (environment variable: PIP_NO_DEPS, PIP_NO_DEPENDENCIES)
• --only-deps — take only the dependencies of the provided requirements into account, not the requirements themselves. Cannot be used in combination with --no-deps, --group, --requirement, or --requirements-from-script. No user-supplied requirements will be handled, even if they were dependencies of other user-supplied requirements. (environment variable: PIP_ONLY_DEPS, PIP_ONLY_DEPENDENCIES)
• -e, --editable <path/url> — install a project in editable mode (i.e. setuptools "develop mode") from a local project path or a VCS url. (environment variable: PIP_EDITABLE)
• --src <dir> — directory to check out editable projects into. The default in a virtualenv is <venv path>/src. The default for global installs is <current dir>/src. (environment variable: PIP_SRC, PIP_SOURCE, PIP_SOURCE_DIR, PIP_SOURCE_DIRECTORY)
• --ignore-requires-python — ignore the Requires-Python information. (environment variable: PIP_IGNORE_REQUIRES_PYTHON)
• --no-build-isolation — disable isolation when building a modern source distribution. Build dependencies specified by PEP 518 must be already installed if this option is used. (environment variable: PIP_NO_BUILD_ISOLATION)
• --check-build-dependencies — check the build dependencies. (environment variable: PIP_CHECK_BUILD_DEPENDENCIES)
• -C, --config-settings <settings> — configuration settings to be passed to the build backend. Settings take the form KEY=VALUE. Use multiple --config-settings options to pass multiple keys to the backend. (environment variable: PIP_CONFIG_SETTINGS)
• --require-hashes — require a hash to check each requirement against, for repeatable installs. This option is implied when any package in a requirements file has a --hash option. (environment variable: PIP_REQUIRE_HASHES)
• --no-require-hashes — do not automatically enable --require-hashes when encountering a requirement with hashes. (environment variable: PIP_NO_REQUIRE_HASHES)
• --progress-bar <progress_bar> — specify whether the progress bar should be used. In auto mode, --quiet will suppress all progress bars. [auto, on, off, raw] (default: auto) (environment variable: PIP_PROGRESS_BAR)
• --group <[path:]group> — install a named dependency-group from a pyproject.toml file. If a path is given, the name of the file must be pyproject.toml. Defaults to using pyproject.toml in the current directory. (environment variable: PIP_GROUP)
• --no-clean — don’t clean up build directories. (environment variable: PIP_NO_CLEAN)

🫶 Author 🫶

pip developers

💖 Copyright 💖

The pip developers

---

okay bestie, that’s the whole page 💅 — from pip, version 26.2, dated Oct 20, 2026. now go lock those deps and be iconic 🎀✨