Setting up a virtualenv: No module named ‘pip’
Useful workaround from the Python bug ticket for anybody else with this issue: Run virtualenv venv –no-setuptools Activate that virtualenv (venv\Scripts\activate) Download and run get-pip.py to manually install pip & setuptools into this virtualenv Continue as normal Alternatively, downgrade to 3.3.3. This should be fixed properly in 3.3.5