mirror of
https://github.com/kennethreitz/python-guide.git
synced 2026-06-05 14:50:19 +00:00
114 lines
4.8 KiB
ReStructuredText
114 lines
4.8 KiB
ReStructuredText
.. _install-windows:
|
|
|
|
Installing Python on Windows
|
|
============================
|
|
|
|
First, download the `latest version <http://python.org/ftp/python/2.7.6/python-2.7.6.msi>`_
|
|
of Python 2.7 from the official Website. If you want to be sure you are installing a fully
|
|
up-to-date version then use the "Windows Installer" link from the home page of the
|
|
`Python.org web site <http://python.org>`_ .
|
|
|
|
The Windows version is provided as an MSI package. To install it manually, just
|
|
double-click the file. The MSI package format allows Windows administrators to
|
|
automate installation with their standard tools.
|
|
|
|
By design, Python installs to a directory with the version number embedded,
|
|
e.g. Python version 2.7 will install at :file:`C:\Python27\`, so that you can
|
|
have multiple versions of Python on the
|
|
same system without conflicts. Of course, only one interpreter can be the
|
|
default application for Python file types. It also does not automatically
|
|
modify the ``PATH`` environment variable, so that you always have control over
|
|
which copy of Python is run.
|
|
|
|
Typing the full path name for a Python interpreter each time quickly gets
|
|
tedious, so add the directories for your default Python version to the PATH.
|
|
Assuming that your Python installation is in :file:`C:\Python27\`, add this to your
|
|
PATH:
|
|
|
|
.. code-block:: console
|
|
|
|
C:\Python27\;C:\Python27\Scripts\
|
|
|
|
You can do this easily by running the following in ``powershell``:
|
|
|
|
.. code-block:: console
|
|
|
|
[Environment]::SetEnvironmentVariable("Path", "$env:Path;C:\Python27\;C:\Python27\Scripts\", "User")
|
|
|
|
The second (:file:`Scripts`) directory receives command files when certain
|
|
packages are installed, so it is a very useful addition.
|
|
You do not need to install or configure anything else to use Python. Having
|
|
said that, I would strongly recommend that you install the tools and libraries
|
|
described in the next section before you start building Python applications for
|
|
real-world use. In particular, you should always install Setuptools, as it
|
|
makes it much easier for you to use other third-party Python libraries.
|
|
|
|
Setuptools + Pip
|
|
----------------
|
|
|
|
The most crucial third-party Python software of all is Setuptools, which
|
|
extends the packaging and installation facilities provided by the distutils in
|
|
the standard library. Once you add Setuptools to your Python system you can
|
|
download and install any compliant Python software product with a single
|
|
command. It also enables you to add this network installation capability to
|
|
your own Python software with very little work.
|
|
|
|
To obtain the latest version of Setuptools for Windows, run the python script
|
|
available here: `ez_setup.py <https://bitbucket.org/pypa/setuptools/raw/bootstrap/ez_setup.py>`_
|
|
|
|
|
|
You'll now have a new command available to you: **easy_install**. It is
|
|
considered by many to be deprecated, so we will install its replacement:
|
|
**pip**. Pip allows for uninstallation of packages, and is actively maintained,
|
|
unlike easy_install.
|
|
|
|
To install pip, run the python script available here:
|
|
`get-pip.py <https://raw.github.com/pypa/pip/master/contrib/get-pip.py>`_
|
|
|
|
|
|
Virtualenv
|
|
----------
|
|
|
|
After Setuptools & Pip, the next development tool that you should install is
|
|
`virtualenv <http://pypi.python.org/pypi/virtualenv/>`_. Use pip
|
|
|
|
.. code-block:: console
|
|
|
|
> pip install virtualenv
|
|
|
|
The virtualenv kit provides the ability to create virtual Python environments
|
|
that do not interfere with either each other, or the main Python installation.
|
|
If you install virtualenv before you begin coding then you can get into the
|
|
habit of using it to create completely clean Python environments for each
|
|
project. This is particularly important for Web development, where each
|
|
framework and application will have many dependencies.
|
|
|
|
|
|
To set up a new Python environment, change the working directory to wherever
|
|
you want to store the environment, and run the virtualenv utility in your
|
|
project's directory
|
|
|
|
.. code-block:: console
|
|
|
|
> virtualenv venv
|
|
|
|
To use an environment, run the :file:`activate.bat` batch file in the :file:`Scripts`
|
|
subdirectory of that environment. Your command prompt will change to show the
|
|
active environment. Once you have finished working in the current virtual
|
|
environment, run the :file:`deactivate.bat` batch file to restore your settings to
|
|
normal.
|
|
|
|
Each new environment automatically includes a copy of ``pip`` in the
|
|
:file:`Scripts` subdirectory, so that you can setup the third-party libraries and
|
|
tools that you want to use in that environment. Put your own code within a
|
|
subdirectory of the environment, however you wish. When you no longer need a
|
|
particular environment, simply copy your code out of it, and then delete the
|
|
main directory for the environment.
|
|
|
|
|
|
|
|
--------------------------------
|
|
|
|
This page is a remixed version of `another guide <http://www.stuartellis.eu/articles/python-development-windows/>`_,
|
|
which is available under the same license.
|