You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/starting/install/osx.rst
+8-33Lines changed: 8 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,44 +77,19 @@ that is recommended over ``easy_install``. It is superior to ``easy_install`` in
77
77
and is actively maintained.
78
78
79
79
80
-
Virtualenv
80
+
Virtual Environments
81
81
----------
82
82
83
-
After Setuptools & Pip, the next development tool that you should install is
84
-
`virtualenv <http://pypi.python.org/pypi/virtualenv/>`_. Use pip
83
+
A Virtual Environment is a tool to keep the dependencies required by different projects
84
+
in separate places, by creating virtual Python environments for them. It solves the
85
+
"Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps
86
+
your global site-packages directory clean and manageable.
85
87
86
-
.. code-block:: console
87
-
88
-
$ pip install virtualenv
89
-
90
-
The virtualenv kit provides the ability to create virtual Python environments
91
-
that do not interfere with either each other, or the main Python installation.
92
-
If you install virtualenv before you begin coding then you can get into the
93
-
habit of using it to create completely clean Python environments for each
94
-
project. This is particularly important for Web development, where each
95
-
framework and application will have many dependencies.
96
-
97
-
To set up a new Python environment, move into the directory where you would
98
-
like to store the environment, and use the ``virtualenv`` utility to create
99
-
the new environment.
100
-
101
-
.. code-block:: console
102
-
103
-
$ virtualenv venv
104
-
105
-
To use an environment, run ``source venv/bin/activate``. Your command prompt
106
-
will change to show the active environment. Once you have finished working in
107
-
the current virtual environment, run ``deactivate`` to restore your settings
108
-
to normal.
88
+
For example, you can work on a project which requires Django 1.3 while also
89
+
maintaining a project which requires Django 1.0.
109
90
110
-
Each new environment automatically includes a copy of ``pip``, so that you can
111
-
setup the third-party libraries and tools that you want to use in that
112
-
environment. Put your own code within a subdirectory of the environment,
113
-
however you wish. When you no longer need a particular environment, simply
114
-
copy your code out of it, and then delete the main directory for the environment.
91
+
To start using and see more information: `Virtual Environments <http://github.com/kennethreitz/python-guide/blob/master/docs/dev/virtualenvs.rst>`_ docs.
115
92
116
-
A useful set of extensions to virtualenv is available in virtualenvwrapper,
117
-
`RTFD <http://virtualenvwrapper.readthedocs.org/en/latest/>`_ to find out more.
0 commit comments