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

Removed references to Setuptools/easy_install in favor of pip. A new Python user hardly needs to know that easy_install ever existed

Browse Source
This commit is contained in:
Adam Nelson
2016-03-14 12:33:49 -04:00
parent 4a3c975eb8
commit 6711e7fde1
1 changed files with 20 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/starting/install/osx.rst
+20 -24
View File
@@ -5,11 +5,11 @@ Installing Python on Mac OS X
The latest version of Mac OS X, El Capitan, **comes with Python 2.7 out of the box**.
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.
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 ``pip``, as it makes
it much easier for you to install and manage other third-party Python libraries.
The version of Python that ships with OS X is great for learning but it's not
good for development. The version shipped with OS X may be out of date from the
@@ -33,11 +33,11 @@ package.
diagnose.
.. note::
If you perform a fresh install of XCode, you will also need to add the
If you perform a fresh install of XCode, you will also need to add the
commandline tools by running ``xcode-select --install`` on the terminal.
While OS X comes with a large number of UNIX utilities, those familiar with
Linux systems will notice one key component missing: a decent package manager.
Linux systems will notice one key component missing: a package manager.
`Homebrew <http://brew.sh>`_ fills this void.
To `install Homebrew <http://brew.sh/#install>`_, open :file:`Terminal` or
@@ -63,37 +63,33 @@ Now, we can install Python 2.7:
$ brew install python
This will take a minute or two.
This will take a minute or two.
Setuptools & Pip
Pip
----------------
Homebrew installs Setuptools and ``pip`` for you.
Homebrew installs ``pip`` for you.
Setuptools enables you to download and install any compliant Python
software over a network (usually the Internet) with a single command
(``easy_install``). It also enables you to add this network installation
capability to your own Python software with very little work.
``pip`` is a tool for easily installing and managing Python packages,
that is recommended over ``easy_install``. It is superior to ``easy_install`` in `several ways <https://python-packaging-user-guide.readthedocs.org/en/latest/pip_easy_install/#pip-vs-easy-install>`_,
``pip`` is a tool for easily installing and managing Python packages, that is
recommended over the deprecated ``easy_install``. It is superior to
``easy_install`` in `several ways
<https://python-packaging-user-guide.readthedocs.org/en/latest/pip_easy_install/#pip-vs-easy-install>`_,
and is actively maintained.
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 (commonly referred to as a 'virtualenv') 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.3 while also
maintaining a project which requires Django 1.0.
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
For example, you can work on a project which requires Django 1.10 while also
maintaining a project which requires Django 1.7.
To start using this and see more information: :ref:`Virtual Environments <virtualenvironments-ref>` docs.
--------------------------------