安装 Python 模块
****************

电子邮箱:
   distutils-sig@python.org

作为一个流行的开源开发项目，Python拥有一个活跃的贡献者和用户支持社区，
这些社区也可以让他们的软件可供其他Python开发人员在开源许可条款下使用。

这允许Python用户有效地共享和协作，从其他人已经创建的解决方案中受益于常
见（有时甚至是罕见的）问题，以及可以提供他们自己的解决方案。

本指南涵盖了分发部分的流程。有关安装其他Python项目的指南，请参阅 安装
指南。

注解: 对于企业和其他机构用户，请注意许多组织都有自己的政策来使用和贡
  献开源 软件。在使用Python提供的分发和安装工具时，请考虑这些政策。


关键术语
========

* "pip" is the preferred installer program. Starting with Python
  2.7.9, it is included by default with the Python binary installers.

* a virtual environment is a semi-isolated Python environment that
  allows packages to be installed for use by a particular application,
  rather than being installed system wide

* "virtualenv" is a third party tools for creating virtual
  environments, it is defaults to installing "pip" into all created
  virtual environments.

* the Python Packaging Index is a public repository of open source
  licensed packages made available for use by other Python users

* the Python Packaging Authority are the group of developers and
  documentation authors responsible for the maintenance and evolution
  of the standard packaging tools and the associated metadata and file
  format standards. They maintain a variety of tools, documentation
  and issue trackers on both GitHub and BitBucket.

* "distutils" is the original build and distribution system first
  added to the Python standard library in 1998. While direct use of
  "distutils" is being phased out, it still laid the foundation for
  the current packaging and distribution infrastructure, and it not
  only remains part of the standard library, but its name lives on in
  other ways (such as the name of the mailing list used to coordinate
  Python packaging standards development).


Basic usage
===========

The standard packaging tools are all designed to be used from the
command line.

The following command will install the latest version of a module and
its dependencies from the Python Packaging Index:

   python -m pip install SomePackage

注解: For POSIX users (including Mac OS X and Linux users), the
  examples in this guide assume the use of a *virtual environment*.
  You may install "virtualenv" to provide such environments using
  either pip ("pip install virtualenv") or through your system package
  manager (commonly called "virtualenv" or "python-virtualenv").For
  Windows users, the examples in this guide assume that the option to
  adjust the system PATH environment variable was selected when
  installing Python.

It’s also possible to specify an exact or minimum version directly on
the command line. When using comparator operators such as ">", "<" or
some other special character which get interpreted by shell, the
package name and the version should be enclosed within double quotes:

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

Normally, if a suitable module is already installed, attempting to
install it again will have no effect. Upgrading existing modules must
be requested explicitly:

   python -m pip install --upgrade SomePackage

More information and resources regarding "pip" and its capabilities
can be found in the Python Packaging User Guide.

参见: Python Packaging User Guide: Installing Python Distribution
  Packages


How do I …?
===========

这是一些常见任务的快速解答或相关链接。


… install "pip" in versions of Python prior to Python 2.7.9?
------------------------------------------------------------

Python only started bundling "pip" with Python 2.7.9. For earlier
versions, "pip" needs to be “bootstrapped” as described in the Python
Packaging User Guide.

参见: Python Packaging User Guide: Requirements for Installing
  Packages


… install packages just for the current user?
---------------------------------------------

Passing the "--user" option to "python -m pip install" will install a
package just for the current user, rather than for all users of the
system.


… install scientific Python packages?
-------------------------------------

A number of scientific Python packages have complex binary
dependencies, and aren’t currently easy to install using "pip"
directly. At this point in time, it will often be easier for users to
install these packages by other means rather than attempting to
install them with "pip".

参见: Python Packaging User Guide: Installing Scientific Packages


… work with multiple versions of Python installed in parallel?
--------------------------------------------------------------

On Linux, Mac OS X and other POSIX systems, use the versioned Python
commands in combination with the "-m" switch to run the appropriate
copy of "pip":

   python2   -m pip install SomePackage  # default Python 2
   python2.7 -m pip install SomePackage  # specifically Python 2.7
   python3   -m pip install SomePackage  # default Python 3
   python3.4 -m pip install SomePackage  # specifically Python 3.4

(appropriately versioned "pip" commands may also be available)

On Windows, use the "py" Python launcher in combination with the "-m"
switch:

   py -2   -m pip install SomePackage  # default Python 2
   py -2.7 -m pip install SomePackage  # specifically Python 2.7
   py -3   -m pip install SomePackage  # default Python 3
   py -3.4 -m pip install SomePackage  # specifically Python 3.4


Common installation issues
==========================


Installing into the system Python on Linux
------------------------------------------

On Linux systems, a Python installation will typically be included as
part of the distribution. Installing into this Python installation
requires root access to the system, and may interfere with the
operation of the system package manager and other components of the
system if a component is unexpectedly upgraded using "pip".

On such systems, it is often better to use a virtual environment or a
per-user installation when installing packages with "pip".


Pip not installed
-----------------

It is possible that "pip" does not get installed by default. One
potential fix is:

   python -m ensurepip --default-pip

There are also additional resources for installing pip.


Installing binary extensions
----------------------------

Python has typically relied heavily on source based distribution, with
end users being expected to compile extension modules from source as
part of the installation process.

With the introduction of support for the binary "wheel" format, and
the ability to publish wheels for at least Windows and Mac OS X
through the Python Packaging Index, this problem is expected to
diminish over time, as users are more regularly able to install pre-
built extensions rather than needing to build them themselves.

Some of the solutions for installing scientific software that is not
yet available as pre-built "wheel" files may also help with obtaining
other binary extensions without needing to build them locally.

参见: Python Packaging User Guide: Binary Extensions
