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 34bfcfc

Browse filesBrowse files
committed
Removed virtualenv and linked to central location
1 parent 1123507 commit 34bfcfc
Copy full SHA for 34bfcfc

File tree

Expand file treeCollapse file tree

1 file changed

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

1 file changed

+8
-35
lines changed

‎docs/starting/install/win.rst

Copy file name to clipboardExpand all lines: docs/starting/install/win.rst
+8-35Lines changed: 8 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -66,45 +66,18 @@ To install pip, run the Python script available here:
6666
`get-pip.py <https://raw.github.com/pypa/pip/master/contrib/get-pip.py>`_
6767

6868

69-
Virtualenv
69+
Virtual Environments
7070
----------
7171

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

75-
.. code-block:: console
76-
77-
> pip install virtualenv
78-
79-
The virtualenv kit provides the ability to create virtual Python environments
80-
that do not interfere with either each other, or the main Python installation.
81-
If you install virtualenv before you begin coding then you can get into the
82-
habit of using it to create completely clean Python environments for each
83-
project. This is particularly important for Web development, where each
84-
framework and application will have many dependencies.
85-
86-
87-
To set up a new Python environment, change the working directory to wherever
88-
you want to store the environment, and run the virtualenv utility in your
89-
project's directory
90-
91-
.. code-block:: console
92-
93-
> virtualenv venv
94-
95-
To use an environment, run the :file:`activate.bat` batch file in the :file:`Scripts`
96-
subdirectory of that environment. Your command prompt will change to show the
97-
active environment. Once you have finished working in the current virtual
98-
environment, run the :file:`deactivate.bat` batch file to restore your settings to
99-
normal.
100-
101-
Each new environment automatically includes a copy of ``pip`` in the
102-
:file:`Scripts` subdirectory, so that you can setup the third-party libraries and
103-
tools that you want to use in that environment. Put your own code within a
104-
subdirectory of the environment, however you wish. When you no longer need a
105-
particular environment, simply copy your code out of it, and then delete the
106-
main directory for the environment.
77+
For example, you can work on a project which requires Django 1.3 while also
78+
maintaining a project which requires Django 1.0.
10779

80+
To start using and see more information: `Virtual Environments <http://github.com/kennethreitz/python-guide/blob/master/docs/dev/virtualenvs.rst>`_ docs.
10881

10982

11083
--------------------------------

0 commit comments

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