Man1 - pip-install.1

pip-install - description of pip install command

IMPORTANT:

#+begin_quote Did this article help?

We are currently doing research to improve pip’s documentation and would love your feedback. Please email us and let us know why you came to this page and what on it helped you and what did not. (Read more about this research)

#+end_quote

Install packages from:

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

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

#+begin_quote

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

#+end_quote

-r, –requirement <file>

Install from the given requirements file. This option can be used multiple times.

-c, –constraint <file>

Constrain versions using the given constraints file. This option can be used multiple times.

–no-deps

Don’t install package dependencies.

–pre

Include pre-release and development versions. By default, pip only finds stable versions.

-e, –editable <path/url>

Install a project in editable mode (i.e. setuptools “develop mode”) from a local project path or a VCS url.

-t, –target <dir>

Install packages into <dir>. By default this will not replace existing files/folders in <dir>. Use –upgrade to replace existing packages in <dir> with new versions.

–platform <platform>

Only use wheels compatible with <platform>. Defaults to the platform of the running system. Use this option multiple times to specify multiple platforms supported by the target interpreter.

–python-version <python_version>

The Python interpreter version to use for wheel and “Requires-Python” compatibility checks. Defaults to a version derived from the running interpreter. The version can be specified using up to three dot-separated integers (e.g. “3” for 3.0.0, “3.7” for 3.7.0, or “3.7.3”). A major-minor version can also be given as a string without dots (e.g. “37” for 3.7.0).

–implementation <implementation>

Only use wheels compatible with Python implementation <implementation>, e.g. ’pp’, ’jy’, ’cp’, or ’ip’. If not specified, then the current interpreter implementation is used. Use ’py’ to force implementation-agnostic wheels.

–abi <abi>

Only use wheels compatible with Python abi <abi>, e.g. ’pypy_41’. If not specified, then the current interpreter abi tag is used. Use this option multiple times to specify multiple abis supported by the target interpreter. Generally you will need to specify –implementation, –platform, and –python-version when using this option.

–user

Install to the Python user install directory for your platform. Typically ~/.local/, or %APPDATA%Python on Windows. (See the Python documentation for site.USER_BASE for full details.)

–root <dir>

Install everything relative to this alternate root directory.

–prefix <dir>

Installation prefix where lib, bin and other top-level folders are placed

–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”.

-U, –upgrade

Upgrade all specified packages to the newest available version. The handling of dependencies depends on the upgrade-strategy used.

–upgrade-strategy <upgrade_strategy>

Determines how dependency upgrading should be handled [default: only-if-needed]. “eager” - dependencies are upgraded regardless of whether the currently installed version satisfies the requirements of the upgraded package(s). “only-if-needed” - are upgraded only when they do not satisfy the requirements of the upgraded package(s).

–force-reinstall

Reinstall all packages even if they are already up-to-date.

-I, –ignore-installed

Ignore the installed packages, overwriting them. This can break your system if the existing package is of a different version or was installed with a different package manager!

–ignore-requires-python

Ignore the Requires-Python information.

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

–use-pep517

Use PEP 517 for building source distributions (use –no-use-pep517 to force legacy behaviour).

–install-option <options>

Extra arguments to be supplied to the setup.py install command (use like –install-option=“–install-scripts=<sys.prefix>/local/bin”). Use multiple –install-option options to pass multiple options to setup.py install. If you are using an option with a directory path, be sure to use absolute path.

–global-option <options>

Extra global options to be supplied to the setup.py call before the install command.

–compile

Compile Python source files to bytecode

–no-compile

Do not compile Python source files to bytecode

–no-warn-script-location

Do not warn when installing scripts outside PATH

–no-warn-conflicts

Do not warn about broken dependencies

–no-binary <format_control>

Do not use binary packages. Can be supplied multiple times, and each time adds to the existing value. Accepts either “:all:” to disable all binary packages, “:none:” to empty the set (notice the colons), or one or more package names with commas between them (no colons). Note that some packages are tricky to compile and may fail to install when this option is used on them.

–only-binary <format_control>

Do not use source packages. Can be supplied multiple times, and each time adds to the existing value. Accepts either “:all:” to disable all source packages, “:none:” to empty the set, or one or more package names with commas between them. Packages without binary distributions will fail to install when this option is used on them.

–prefer-binary

Prefer older binary packages over newer source packages.

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

–progress-bar <progress_bar>

Specify type of progress to be displayed [off|on|ascii|pretty|emoji] (default: on)

–no-clean

Don’t clean up build directories.

IMPORTANT:

#+begin_quote Did this article help?

We are currently doing research to improve pip’s documentation and would love your feedback. Please email us and let us know:

#+begin_quote

1. What problem were you trying to solve when you came to this page?
2. What content was useful?
3. What content was not useful?

#+end_quote #+end_quote

pip developers

2008-2021, PyPA