Skip to content


mention the useful bin/activate command #759

wants to merge 2 commits into from

2 participants


No description provided.

Pylons Project member

I hesitate to recommend "activate" because I've found that people run it once, and forget to run it during the next session, and they get very confused when things behave differently. So I've taken to just neglecting to mention it, and telling them to run the virtualenv bin/python directly, which has seemed to work out better ultimately because they understand how it works.


One reason I added this is because I saw it in one of the Pyramid tutorials, so I added it there to avoid duplication.

@tshepang tshepang added a commit that referenced this pull request
@tshepang tshepang Reduce duplicated installation instructions from the tutorials
* This also removes the mention of running 'source bin/activate' (see #759).
Pylons Project member

I'm going to close this for now, it's appreciated, though.

@mcdonc mcdonc closed this
@tshepang tshepang deleted the unknown repository branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Jan 1, 2013
  1. @tshepang
Commits on Jan 2, 2013
  1. @tshepang
This page is out of date. Refresh to see the latest.
Showing with 7 additions and 0 deletions.
  1. +7 −0 docs/narr/install.rst
7 docs/narr/install.rst
@@ -308,6 +308,13 @@ following:
You should perform any following commands that mention a "bin"
directory from within the ``env`` virtualenv dir.
+If you use bash, consider using ``source bin/activate`` to make your
+shell environment wired to use the virtualenv.
+This means, for example, instead of running ``bin/python`` to run the
+interpreter in this isolated environment, you will run ``python``.
+This will only work as long as you remain in the same bash session.
Installing :app:`Pyramid` Into the Virtual Python Environment
Something went wrong with that request. Please try again.