Setting up a virtualenv: No module named 'pip'

Question

I have a fresh install of Python 3.3.4 on a Windows Server 2008 R2 machine. I've successfully installed the latest versions of Setuptools, Pip and Virtualenv globally: ``` python ez_setup.py easy_install pip pip install virtualenv ``` Now when I try to set up a virtualenv using `virtualenv ENV` I get the following stack trace: ``` New python executable in ENV\Scripts\python.exe Installing setuptools, pip... Complete output from command [path redacted]\ENV\Scripts\python.exe -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip: Traceback (most recent call last): File "", line 1, in ImportError: No module named 'pip' ---------------------------------------- ...Installing setuptools, pip...done. Traceback (most recent call last): File "C:\Python33\lib\runpy.py", line 160, in _run_module_as_main "__main__", fname, loader, pkg_name) File "C:\Python33\lib\runpy.py", line 73, in _run_code exec(code, run_globals) File "C:\Python33\Scripts\virtualenv.exe\__main__.p…

Accepted Answer

Annoyingly, it looks like this might be a Python bug. https://github.com/pypa/virtualenv/issues/564 references http://bugs.python.org/issue20621, which is still open but looks like it's going to be fixed in 3.3.5.

Dropping my Python installation back down to 3.3.3 fixed the issue.

Setting up a virtualenv: No module named 'pip'

Solution

Problem