mirror of
https://github.com/kennethreitz/python-guide.git
synced 2026-06-05 14:50:19 +00:00
update python 2 guides
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
.. _install-linux:
|
||||
|
||||
Installing Python on Linux
|
||||
==========================
|
||||
Installing Python 2 on Linux
|
||||
============================
|
||||
|
||||
The latest versions of CentOS, Fedora, Redhat Enterprise (RHEL) and Ubuntu
|
||||
The latest versions of CentOS, Fedora, Redhat Enterprise (RHEL) and Ubuntu
|
||||
**come with Python 2.7 out of the box**.
|
||||
|
||||
To see which version of Python you have installed, open a command prompt and run
|
||||
@@ -32,11 +32,11 @@ Setuptools & Pip
|
||||
|
||||
The two most crucial third-party Python packages are `setuptools <https://pypi.python.org/pypi/setuptools>`_ and `pip <https://pip.pypa.io/en/stable/>`_.
|
||||
|
||||
Once installed, you can download, install and uninstall any compliant Python software
|
||||
product with a single command. It also enables you to add this network installation
|
||||
Once installed, you can download, install and uninstall 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.
|
||||
|
||||
Python 2.7.9 and later (on the python2 series), and Python 3.4 and later include
|
||||
Python 2.7.9 and later (on the python2 series), and Python 3.4 and later include
|
||||
pip by default.
|
||||
|
||||
To see if pip is installed, open a command prompt and run
|
||||
@@ -50,15 +50,15 @@ To install pip, `follow the official pip installation guide <https://pip.pypa.io
|
||||
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
|
||||
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.
|
||||
|
||||
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
|
||||
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
|
||||
|
||||
You can also use :ref:`virtualenvwrapper <virtualenvwrapper-ref>` to make it easier to
|
||||
manage your virtual environments.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
.. _install-osx:
|
||||
|
||||
Installing Python on Mac OS X
|
||||
=============================
|
||||
Installing Python 2 on Mac OS X
|
||||
===============================
|
||||
|
||||
.. note::
|
||||
Check out our :ref:`guide for installing Python 3 on OS X<install3-osx>`.
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
.. _install-windows:
|
||||
|
||||
Installing Python on Windows
|
||||
============================
|
||||
Installing Python 2 on Windows
|
||||
==============================
|
||||
|
||||
First, download the `latest version <https://www.python.org/ftp/python/2.7.12/python-2.7.12.msi>`_
|
||||
of Python 2.7 from the official Website. If you want to be sure you are installing a fully
|
||||
First, download the `latest version <https://www.python.org/ftp/python/2.7.13/python-2.7.13.msi>`_
|
||||
of Python 2.7 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>`_ .
|
||||
|
||||
@@ -35,6 +35,8 @@ You can do this easily by running the following in ``powershell``:
|
||||
|
||||
[Environment]::SetEnvironmentVariable("Path", "$env:Path;C:\Python27\;C:\Python27\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
|
||||
@@ -69,15 +71,15 @@ To install pip, run the Python script available here:
|
||||
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
|
||||
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.
|
||||
|
||||
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
|
||||
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
|
||||
|
||||
|
||||
--------------------------------
|
||||
|
||||
Reference in New Issue
Block a user