Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 86148b3

Browse filesBrowse files
committed
Removed virtualenv and linked to central location
1 parent e4025c1 commit 86148b3
Copy full SHA for 86148b3

File tree

Expand file treeCollapse file tree

1 file changed

+8
-31
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+8
-31
lines changed

‎docs/starting/install/linux.rst

Copy file name to clipboardExpand all lines: docs/starting/install/linux.rst
+8-31Lines changed: 8 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -45,41 +45,18 @@ To install pip, simply open a command prompt and run
4545
$ easy_install pip
4646
4747
48-
Virtualenv
48+
Virtual Environments
4949
----------
5050

51-
After Setuptools & Pip, the next development tool that you should install is
52-
`virtualenv <http://pypi.python.org/pypi/virtualenv/>`_. Use pip
51+
A Virtual Environment is a tool to keep the dependencies required by different projects
52+
in separate places, by creating virtual Python environments for them. It solves the
53+
"Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps
54+
your global site-packages directory clean and manageable.
5355

54-
.. code-block:: console
55-
56-
$ pip install virtualenv
57-
58-
The virtualenv kit provides the ability to create virtual Python environments
59-
that do not interfere with either each other, or the main Python installation.
60-
If you install virtualenv before you begin coding then you can get into the
61-
habit of using it to create completely clean Python environments for each
62-
project. This is particularly important for Web development, where each
63-
framework and application will have many dependencies.
64-
65-
To set up a new Python environment, change the working directory to where ever
66-
you want to store the environment, and run the virtualenv utility in your
67-
project's directory
68-
69-
.. code-block:: console
70-
71-
$ virtualenv venv
72-
73-
To use an environment, run ``source venv/bin/activate``. Your command prompt
74-
will change to show the active environment. Once you have finished working in
75-
the current virtual environment, run ``deactivate`` to restore your settings
76-
to normal.
56+
For example, you can work on a project which requires Django 1.3 while also
57+
maintaining a project which requires Django 1.0.
7758

78-
Each new environment automatically includes a copy of ``pip``, so that you can
79-
setup the third-party libraries and tools that you want to use in that
80-
environment. Put your own code within a subdirectory of the environment,
81-
however you wish. When you no longer need a particular environment, simply
82-
copy your code out of it, and then delete the main directory for the environment.
59+
To start using and see more information: `Virtual Environments <http://github.com/kennethreitz/python-guide/blob/master/docs/dev/virtualenvs.rst>`_ docs.
8360

8461

8562
--------------------------------

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.