Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 25
    The virtualenv upgrade worked, but for some reason I also had to be explicit about python3 executable with virtualenv -p $(which python3) envname Commented Nov 7, 2014 at 22:15
  • 2
    is it possible to just change the current environment's python interpreter rather than creating a new environment? Commented Aug 28, 2016 at 21:36
  • On Raspbian Jessie 'virtualenv --no-site-packages python3.4' worked. --distribute is deprecated and -p doesn't seem necessary since virtualenv uses python3. Commented Nov 10, 2017 at 13:04
  • 1
    Why is it that after running virtualenv -p python3 my_virtual_env, python3 is accessible from outside the virtual environment also? Commented Apr 17, 2018 at 9:57
  • 2
    After that you need to use cd envname and run source ./bin/activate - this will run virtual environment. Use deactivate in order to exit from this virtual environment. Commented Mar 12, 2020 at 12:21