kennethreitz/python-guide
1
0
Fork 0
mirror of https://github.com/kennethreitz/python-guide.git synced 2026-06-05 23:00:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

update python 2 guides

Browse Source
This commit is contained in:
Kenneth Reitz
2017-04-13 10:43:58 -04:00
parent d3d2fcc496
commit 0c97ce5a31
3 changed files with 22 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/starting/install/linux.rst
+10 -10
View File
@@ -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.