Установка пакетов python на windows

Requirements for Installing Packages¶

This section describes the steps to follow before installing other Python
packages.

>>> python3 --version
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'python3' is not defined

In [1]: import sys
        !{sys.executable} --version
Python 3.6.3

python3 -m ensurepip --default-pip

py -m ensurepip --default-pip

python3 -m pip install --upgrade pip setuptools wheel

py -m pip install --upgrade pip setuptools wheel

python3 -m venv tutorial_env
source tutorial_env/bin/activate

py -m venv tutorial_env
tutorial_env\Scripts\activate

Creating Virtual Environments¶

Python “Virtual Environments” allow Python packages to be installed in an isolated location for a particular application,
rather than being installed globally. If you are looking to safely install
global command line tools,
see Installing stand alone command line tools.

Imagine you have an application that needs version 1 of LibFoo, but another
application requires version 2. How can you use both these applications? If you
install everything into /usr/lib/python3.6/site-packages (or whatever your
platform’s standard location is), it’s easy to end up in a situation where you
unintentionally upgrade an application that shouldn’t be upgraded.

Or more generally, what if you want to install an application and leave it be?
If an application works, any change in its libraries or the versions of those
libraries can break the application.

Also, what if you can’t install packages into the
global site-packages directory? For instance, on a shared host.

In all these cases, virtual environments can help you. They have their own
installation directories and they don’t share libraries with other virtual
environments.

Currently, there are two common tools for creating Python virtual environments:

• venv is available by default in Python 3.3 and later, and installs
  pip into created virtual environments in Python 3.4 and later
  (Python versions prior to 3.12 also installed Setuptools).

• virtualenv needs to be installed separately, but supports Python 2.7+
  and Python 3.3+, and pip, Setuptools and wheel are
  installed into created virtual environments by default. Note that setuptools is no longer
  included by default starting with Python 3.12 (and virtualenv follows this behavior).

The basic usage is like so:

Using venv:

python3 -m venv <DIR>
source <DIR>/bin/activate

py -m venv <DIR>
<DIR>\Scripts\activate

Using virtualenv:

python3 -m virtualenv <DIR>
source <DIR>/bin/activate

virtualenv <DIR>
<DIR>\Scripts\activate

For more information, see the venv docs or
the virtualenv docs.

The use of source under Unix shells ensures
that the virtual environment’s variables are set within the current
shell, and not in a subprocess (which then disappears, having no
useful effect).

In both of the above cases, Windows users should not use the
source command, but should rather run the activate
script directly from the command shell like so:

Managing multiple virtual environments directly can become tedious, so the
dependency management tutorial introduces a
higher level tool, Pipenv, that automatically manages a separate
virtual environment for each project and application that you work on.

Use pip for Installing¶

pip is the recommended installer. Below, we’ll cover the most common
usage scenarios. For more detail, see the pip docs,
which includes a complete Reference Guide.

Installing from PyPI¶

The most common usage of pip is to install from the Python Package
Index using a requirement specifier. Generally speaking, a requirement specifier is
composed of a project name followed by an optional version specifier. A full description of the supported specifiers can be
found in the Version specifier specification.
Below are some examples.

To install the latest version of “SomeProject”:

python3 -m pip install "SomeProject"

py -m pip install "SomeProject"

To install a specific version:

python3 -m pip install "SomeProject==1.4"

py -m pip install "SomeProject==1.4"

To install greater than or equal to one version and less than another:

python3 -m pip install "SomeProject>=1,<2"

py -m pip install "SomeProject>=1,<2"

To install a version that’s compatible
with a certain version: [4]

python3 -m pip install "SomeProject~=1.4.2"

py -m pip install "SomeProject~=1.4.2"

In this case, this means to install any version “==1.4.*” version that’s also
“>=1.4.2”.

Source Distributions vs Wheels¶

pip can install from either Source Distributions (sdist) or Wheels, but if both are present
on PyPI, pip will prefer a compatible wheel. You can override
pip`s default behavior by e.g. using its –no-binary option.

Wheels are a pre-built distribution format that provides faster installation compared to Source
Distributions (sdist), especially when a
project contains compiled extensions.

If pip does not find a wheel to install, it will locally build a wheel
and cache it for future installs, instead of rebuilding the source distribution
in the future.

Upgrading packages¶

Upgrade an already installed SomeProject to the latest from PyPI.

python3 -m pip install --upgrade SomeProject

py -m pip install --upgrade SomeProject

Installing to the User Site¶

To install packages that are isolated to the
current user, use the --user flag:

python3 -m pip install --user SomeProject

py -m pip install --user SomeProject

For more information see the User Installs section
from the pip docs.

Note that the --user flag has no effect when inside a virtual environment
— all installation commands will affect the virtual environment.

If SomeProject defines any command-line scripts or console entry points,
--user will cause them to be installed inside the user base’s binary
directory, which may or may not already be present in your shell’s
PATH. (Starting in version 10, pip displays a warning when
installing any scripts to a directory outside PATH.) If the scripts
are not available in your shell after installation, you’ll need to add the
directory to your PATH:

• On Linux and macOS you can find the user base binary directory by running
  python -m site --user-base and adding bin to the end. For example,
  this will typically print ~/.local (with ~ expanded to the absolute
  path to your home directory) so you’ll need to add ~/.local/bin to your
  PATH. You can set your PATH permanently by modifying ~/.profile.

• On Windows you can find the user base binary directory by running py -m
site --user-site and replacing site-packages with Scripts. For
  example, this could return
  C:\Users\Username\AppData\Roaming\Python36\site-packages so you would
  need to set your PATH to include
  C:\Users\Username\AppData\Roaming\Python36\Scripts. You can set your user
  PATH permanently in the Control Panel. You may need to log out for the
  PATH changes to take effect.

Requirements files¶

Install a list of requirements specified in a Requirements File.

python3 -m pip install -r requirements.txt

py -m pip install -r requirements.txt

Installing from VCS¶

Install a project from VCS in “editable” mode. For a full breakdown of the
syntax, see pip’s section on VCS Support.

python3 -m pip install -e SomeProject @ git+https://git.repo/some_pkg.git          # from git
python3 -m pip install -e SomeProject @ hg+https://hg.repo/some_pkg                # from mercurial
python3 -m pip install -e SomeProject @ svn+svn://svn.repo/some_pkg/trunk/         # from svn
python3 -m pip install -e SomeProject @ git+https://git.repo/some_pkg.git@feature  # from a branch

py -m pip install -e SomeProject @ git+https://git.repo/some_pkg.git          # from git
py -m pip install -e SomeProject @ hg+https://hg.repo/some_pkg                # from mercurial
py -m pip install -e SomeProject @ svn+svn://svn.repo/some_pkg/trunk/         # from svn
py -m pip install -e SomeProject @ git+https://git.repo/some_pkg.git@feature  # from a branch

Installing from other Indexes¶

Install from an alternate index

python3 -m pip install --index-url http://my.package.repo/simple/ SomeProject

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

Search an additional index during install, in addition to PyPI

python3 -m pip install --extra-index-url http://my.package.repo/simple SomeProject

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

Installing from a local src tree¶

Installing from local src in
Development Mode,
i.e. in such a way that the project appears to be installed, but yet is
still editable from the src tree.

python3 -m pip install -e <path>

py -m pip install -e <path>

You can also install normally from src

python3 -m pip install <path>

Installing from local archives¶

Install a particular source archive file.

python3 -m pip install ./downloads/SomeProject-1.0.4.tar.gz

py -m pip install ./downloads/SomeProject-1.0.4.tar.gz

Install from a local directory containing archives (and don’t check PyPI)

python3 -m pip install --no-index --find-links=file:///local/dir/ SomeProject
python3 -m pip install --no-index --find-links=/local/dir/ SomeProject
python3 -m pip install --no-index --find-links=relative/dir/ SomeProject

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

Installing from other sources¶

To install from other data sources (for example Amazon S3 storage)
you can create a helper application that presents the data
in a format compliant with the simple repository API:,
and use the --extra-index-url flag to direct pip to use that index.

./s3helper --port=7777
python -m pip install --extra-index-url http://localhost:7777 SomeProject

Installing Prereleases¶

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

python3 -m pip install --pre SomeProject

py -m pip install --pre SomeProject

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.

(environment variable: PIP_REQUIREMENT)

-c, —constraint <file>¶

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

(environment variable: PIP_CONSTRAINT)

—no-deps¶

Don’t install package dependencies.

(environment variable: PIP_NO_DEPS, PIP_NO_DEPENDENCIES)

—pre¶

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

(environment variable: PIP_PRE)

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

—dry-run¶

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

(environment variable: PIP_DRY_RUN)

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

(environment variable: PIP_TARGET)

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

(environment variable: PIP_PLATFORM)

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

(environment variable: PIP_PYTHON_VERSION)

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

(environment variable: PIP_IMPLEMENTATION)

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

(environment variable: PIP_ABI)

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

(environment variable: PIP_USER)

—root <dir>¶

Install everything relative to this alternate root directory.

(environment variable: PIP_ROOT)

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

(environment variable: PIP_PREFIX)

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

-U, —upgrade¶

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

(environment variable: PIP_UPGRADE)

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

(environment variable: PIP_UPGRADE_STRATEGY)

—force-reinstall¶

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

(environment variable: PIP_FORCE_REINSTALL)

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

(environment variable: PIP_IGNORE_INSTALLED)

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

—use-pep517¶

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

(environment variable: PIP_USE_PEP517)

—check-build-dependencies¶

Check the build dependencies when PEP517 is used.

(environment variable: PIP_CHECK_BUILD_DEPENDENCIES)

—break-system-packages¶

Allow pip to modify an EXTERNALLY-MANAGED Python installation

(environment variable: PIP_BREAK_SYSTEM_PACKAGES)

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

(environment variable: PIP_CONFIG_SETTINGS)

—global-option <options>¶

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

(environment variable: PIP_GLOBAL_OPTION)

—compile¶

Compile Python source files to bytecode

(environment variable: PIP_COMPILE)

—no-compile¶

Do not compile Python source files to bytecode

(environment variable: PIP_NO_COMPILE)

—no-warn-script-location¶

Do not warn when installing scripts outside PATH

(environment variable: PIP_NO_WARN_SCRIPT_LOCATION)

—no-warn-conflicts¶

Do not warn about broken dependencies

(environment variable: PIP_NO_WARN_CONFLICTS)

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

(environment variable: PIP_NO_BINARY)

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

(environment variable: PIP_ONLY_BINARY)

—prefer-binary¶

Prefer binary packages over source packages, even if the source packages are newer.

(environment variable: PIP_PREFER_BINARY)

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

—progress-bar <progress_bar>¶

Specify whether the progress bar should be used [on, off, raw] (default: on)

(environment variable: PIP_PROGRESS_BAR)

—root-user-action <root_user_action>¶

Action if pip is run as a root user [warn, ignore] (default: warn)

(environment variable: PIP_ROOT_USER_ACTION)

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

(environment variable: PIP_REPORT)

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

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

(environment variable: PIP_INDEX_URL, PIP_PYPI_URL)

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

(environment variable: PIP_EXTRA_INDEX_URL)

—no-index¶

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

(environment variable: PIP_NO_INDEX)

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

(environment variable: PIP_FIND_LINKS)

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, i.e., optional dependencies
   (specification).

   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 direct references
   (specification).

   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