Python установка через pip windows

Usage#

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

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

Description#

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.

$ python -m pip install quux
...
Installing collected packages baz, bar, foo, quux

$ python -m pip install bar
...
Installing collected packages foo, baz, bar

C:\> py -m pip install quux
...
Installing collected packages baz, bar, foo, quux

C:\> py -m pip install bar
...
Installing collected packages foo, baz, bar

Options#

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

—dry-run#

Don’t actually install anything, just print what would be. Can be used in combination with —ignore-installed to ‘resolve’ the requirements.

-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. Note that the resulting installation may contain scripts and other resources which reference the Python interpreter of pip, and not that of --prefix. See also the --python option if the intention is to install packages into another (possibly pip-free) environment.

—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).

—check-build-dependencies#

Check the build dependencies when PEP517 is used.

—break-system-packages#

Allow pip to modify an EXTERNALLY-MANAGED Python installation

-C, —config-settings <settings>#

Configuration settings to be passed to the PEP 517 build backend. Settings take the form KEY=VALUE. Use multiple —config-settings options to pass multiple keys to the backend.

—global-option <options>#

Extra global options to be supplied to the setup.py call before the install or bdist_wheel 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 whether the progress bar should be used [on, off] (default: on)

—root-user-action <root_user_action>#

Action if pip is run as a root user. By default, a warning message is shown.

—report <file>#

Generate a JSON file describing what pip did to install the provided requirements. Can be used in combination with —dry-run and —ignore-installed to ‘resolve’ the requirements. When — is used as file name it writes to stdout. When writing to stdout, please combine with the —quiet option to avoid mixing pip logging output with JSON output.

—no-clean#

Don’t clean up build directories.

-i, —index-url <url>#

Base URL of the Python Package Index (default https://pypi.org/simple). This should point to a repository compliant with PEP 503 (the simple repository API) or a local directory laid out in the same format.

Extra URLs of package indexes to use in addition to —index-url. Should follow the same rules as —index-url.

—no-index#

Ignore package index (only looking at —find-links URLs instead).

-f, —find-links <url>#

If a URL or path to an html file, then parse for links to archives such as sdist (.tar.gz) or wheel (.whl) files. If a local path or file:// URL that’s a directory, then look for archives in the directory listing. Links to VCS project URLs are not supported.

Examples#

1. Install SomePackage and its dependencies from PyPI using Requirement Specifiers

   Unix/macOS

   python -m pip install SomePackage            # latest version
   python -m pip install 'SomePackage==1.0.4'   # specific version
   python -m pip install 'SomePackage>=1.0.4'   # minimum version
   

   Windows

   py -m pip install SomePackage            # latest version
   py -m pip install "SomePackage==1.0.4"   # specific version
   py -m pip install "SomePackage>=1.0.4"   # minimum version
   

2. Install a list of requirements specified in a file. See the Requirements files.

   Unix/macOS

   python -m pip install -r requirements.txt
   

   Windows

   py -m pip install -r requirements.txt
   

3. Upgrade an already installed SomePackage to the latest from PyPI.

   Unix/macOS

   python -m pip install --upgrade SomePackage
   

   Windows

   py -m pip install --upgrade SomePackage
   

   Note

   This will guarantee an update to SomePackage as it is a direct
   requirement, and possibly upgrade dependencies if their installed
   versions do not meet the minimum requirements of SomePackage.
   Any non-requisite updates of its dependencies (indirect requirements)
   will be affected by the --upgrade-strategy command.

4. Install a local project in “editable” mode. See the section on Editable Installs.

   Unix/macOS

   python -m pip install -e .                # project in current directory
   python -m pip install -e path/to/project  # project in another directory
   

   Windows

   py -m pip install -e .                 # project in current directory
   py -m pip install -e path/to/project   # project in another directory
   

5. Install a project from VCS

   Unix/macOS

   python -m pip install 'SomeProject@git+https://git.repo/some_pkg.git@1.3.1'
   

   Windows

   py -m pip install "SomeProject@git+https://git.repo/some_pkg.git@1.3.1"
   

6. Install a project from VCS in “editable” mode. See the sections on VCS Support and Editable Installs.

   Unix/macOS

   python -m pip install -e 'git+https://git.repo/some_pkg.git#egg=SomePackage'          # from git
   python -m pip install -e 'hg+https://hg.repo/some_pkg.git#egg=SomePackage'            # from mercurial
   python -m pip install -e 'svn+svn://svn.repo/some_pkg/trunk/#egg=SomePackage'         # from svn
   python -m pip install -e 'git+https://git.repo/some_pkg.git@feature#egg=SomePackage'  # from 'feature' branch
   python -m pip install -e 'git+https://git.repo/some_repo.git#egg=subdir&subdirectory=subdir_path' # install a python package from a repo subdirectory
   

   Windows

   py -m pip install -e "git+https://git.repo/some_pkg.git#egg=SomePackage"          # from git
   py -m pip install -e "hg+https://hg.repo/some_pkg.git#egg=SomePackage"            # from mercurial
   py -m pip install -e "svn+svn://svn.repo/some_pkg/trunk/#egg=SomePackage"         # from svn
   py -m pip install -e "git+https://git.repo/some_pkg.git@feature#egg=SomePackage"  # from 'feature' branch
   py -m pip install -e "git+https://git.repo/some_repo.git#egg=subdir&subdirectory=subdir_path" # install a python package from a repo subdirectory
   

7. Install a package with extras.

   Unix/macOS

   python -m pip install 'SomePackage[PDF]'
   python -m pip install 'SomePackage[PDF] @ git+https://git.repo/SomePackage@main#subdirectory=subdir_path'
   python -m pip install '.[PDF]'  # project in current directory
   python -m pip install 'SomePackage[PDF]==3.0'
   python -m pip install 'SomePackage[PDF,EPUB]'  # multiple extras
   

   Windows

   py -m pip install "SomePackage[PDF]"
   py -m pip install "SomePackage[PDF] @ git+https://git.repo/SomePackage@main#subdirectory=subdir_path"
   py -m pip install ".[PDF]"  # project in current directory
   py -m pip install "SomePackage[PDF]==3.0"
   py -m pip install "SomePackage[PDF,EPUB]"  # multiple extras
   

8. Install a particular source archive file.

   Unix/macOS

   python -m pip install './downloads/SomePackage-1.0.4.tar.gz'
   python -m pip install 'http://my.package.repo/SomePackage-1.0.4.zip'
   

   Windows

   py -m pip install "./downloads/SomePackage-1.0.4.tar.gz"
   py -m pip install "http://my.package.repo/SomePackage-1.0.4.zip"
   

9. Install a particular source archive file following PEP 440 direct references.

   Unix/macOS

   python -m pip install 'SomeProject@http://my.package.repo/SomeProject-1.2.3-py33-none-any.whl'
   python -m pip install 'SomeProject @ http://my.package.repo/SomeProject-1.2.3-py33-none-any.whl'
   python -m pip install 'SomeProject@http://my.package.repo/1.2.3.tar.gz'
   

   Windows

   py -m pip install "SomeProject@http://my.package.repo/SomeProject-1.2.3-py33-none-any.whl"
   py -m pip install "SomeProject @ http://my.package.repo/SomeProject-1.2.3-py33-none-any.whl"
   py -m pip install "SomeProject@http://my.package.repo/1.2.3.tar.gz"
   

10. Install from alternative package repositories.

    Install from a different index, and not PyPI

    Unix/macOS

    python -m pip install --index-url http://my.package.repo/simple/ SomePackage
    

    Windows

    py -m pip install --index-url http://my.package.repo/simple/ SomePackage
    

    Install from a local flat directory containing archives (and don’t scan indexes):

    Unix/macOS

    python -m pip install --no-index --find-links=file:///local/dir/ SomePackage
    python -m pip install --no-index --find-links=/local/dir/ SomePackage
    python -m pip install --no-index --find-links=relative/dir/ SomePackage
    

    Windows

    py -m pip install --no-index --find-links=file:///local/dir/ SomePackage
    py -m pip install --no-index --find-links=/local/dir/ SomePackage
    py -m pip install --no-index --find-links=relative/dir/ SomePackage
    

    Search an additional index during install, in addition to PyPI

    Warning

    Using this option to search for packages which are not in the main
    repository (such as private packages) is unsafe, per a security
    vulnerability called
    dependency confusion:
    an attacker can claim the package on the public repository in a way that
    will ensure it gets chosen over the private package.

    Unix/macOS

    python -m pip install --extra-index-url http://my.package.repo/simple SomePackage
    

    Windows

    py -m pip install --extra-index-url http://my.package.repo/simple SomePackage
    

11. Find pre-release and development versions, in addition to stable versions. By default, pip only finds stable versions.

    Unix/macOS

    python -m pip install --pre SomePackage
    

    Windows

    py -m pip install --pre SomePackage
    

12. Install packages from source.

    Do not use any binary packages

    Unix/macOS

    python -m pip install SomePackage1 SomePackage2 --no-binary :all:
    

    Windows

    py -m pip install SomePackage1 SomePackage2 --no-binary :all:
    

    Specify SomePackage1 to be installed from source:

    Unix/macOS

    python -m pip install SomePackage1 SomePackage2 --no-binary SomePackage1
    

    Windows

    py -m pip install SomePackage1 SomePackage2 --no-binary SomePackage1