mirror of
https://github.com/kennethreitz/python-guide.git
synced 2026-06-05 14:50:19 +00:00
106 lines
4.1 KiB
ReStructuredText
106 lines
4.1 KiB
ReStructuredText
.. _install3-windows:
|
|
|
|
Installing Python 3 on Windows
|
|
==============================
|
|
|
|
.. image:: https://farm5.staticflickr.com/4276/34435689480_2e6f358510_k_d.jpg
|
|
|
|
First, download the `latest version <https://www.python.org/ftp/python/3.6.2/python-3.6.2.exe>`_
|
|
of Python 3.6 from the official website. If you want to be sure you are installing a fully
|
|
up-to-date version, click the Downloads > Windows link from the home page of the
|
|
`Python.org web site <http://python.org>`_ .
|
|
|
|
By design, Python installs to a directory with the version number embedded,
|
|
e.g. Python version 3.6 will install at :file:`C:\\Python36\\`, 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 :envvar:`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 :envvar:`PATH`.
|
|
Assuming that your Python installation is in :file:`C:\\Python36\\`, add this to your
|
|
:envvar:`PATH`:
|
|
|
|
.. code-block:: console
|
|
|
|
C:\Python36\;C:\Python36\Scripts\
|
|
|
|
You can do this easily by running the following in ``powershell``:
|
|
|
|
.. code-block:: console
|
|
|
|
[Environment]::SetEnvironmentVariable("Path", "$env:Path;C:\Python36\;C:\Python36\Scripts\", "User")
|
|
|
|
This is also an option during the installation process.
|
|
|
|
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.
|
|
|
|
Working with Python 3
|
|
---------------------
|
|
|
|
At this point, you may also have Python 2.7 installed.
|
|
|
|
.. code-block:: console
|
|
|
|
$ python
|
|
|
|
This will launch the Python 2 interpreter.
|
|
|
|
.. code-block:: console
|
|
|
|
$ python3
|
|
|
|
This will launch the Python 3 interpreter.
|
|
|
|
|
|
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://bootstrap.pypa.io/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>`_
|
|
|
|
|
|
Pipenv & Virtual Environments
|
|
-----------------------------
|
|
|
|
The next step it to install Pipenv, so you can install dependencies and manage virtual environments.
|
|
|
|
A Virtual Environment is a tool to keep the dependencies required by different projects
|
|
in separate places, by creating virtual Python environments for them. It solves the
|
|
"Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps
|
|
your global site-packages directory clean and manageable.
|
|
|
|
For example, you can work on a project which requires Django 1.10 while also
|
|
maintaining a project which requires Django 1.8.
|
|
|
|
So, onward! To the :ref:`Pipenv & Virtual Environments <virtualenvironments-ref>` docs!
|
|
|
|
--------------------------------
|
|
|
|
This page is a remixed version of `another guide <http://www.stuartellis.eu/articles/python-development-windows/>`_,
|
|
which is available under the same license.
|