Forums

I ran into the issue of python3.4 -m venv env_name not working.

I tried following the hack given here:

https://www.pythonanywhere.com/forums/topic/1432/

https://www.pythonanywhere.com/forums/topic/994/

But this

python3.4 -m venv env_name --without-pip
source env_name/bin/activate
python3.4 -m ensurepip

Just results in...

/home/SuaveSteve/.virtualenvs/MoonThing/bin/python3.4: No module named ensurepip

I've used virtualenvwrapper in the meantime.

I'm not entirely sure but seems like you may also need to do an extra step for now