Permalink
Browse files

dev env cleanup

  • Loading branch information...
1 parent d05c08c commit 51c32b84ec5e08b1fd0ed8d1dd98f0a6c990b76d @kennethreitz kennethreitz committed Dec 30, 2011
Showing with 4 additions and 22 deletions.
  1. +4 −22 docs/starting/dev-env.rst
View
@@ -113,21 +113,12 @@ It solves the "Project X depends on version 1.x but, Project Y needs 4.x" dilemm
a folder which contains all the necessary executables to contain the
packages that a Python project would need. An example workflow is given.
-Install virtualenv
-
-::
+Install virtualenv::
$ pip install virtualenv
-or, depending on what's available
-
-::
- $ easy_install virtualenv
-
-Create a virtual environment for a project
-
-::
+Create a virtual environment for a project::
$ cd my_project
$ virtualenv venv
@@ -138,25 +129,16 @@ library which you can use to install other packages. The name of the
virtual environment (in this case, it was ``venv``) can be anything;
omitting the name will place the files in the current directory instead.
-In order the start using the virtual environment, run
-
-::
+In order the start using the virtual environment, run::
$ source venv/bin/activate
-or
-
-::
-
- $ . venv/bin/activate
The name of the current virtual environment will now appear on the left
of the prompt (e.g. ``(venv)Your-Computer:your_project UserName$``) to
let you know that it's active. From now on, any package that you install
using ``pip`` will be placed in the venv folder, isolated from the global
-Python installation. Install packages as usual.
-
-::
+Python installation. Install packages as usual::
$ pip install requests

0 comments on commit 51c32b8

Please sign in to comment.