Menu
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 "<string>", line 1, in <module> 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__.py", line 9, in <module> File "C:\Python33\lib\site-packages\virtualenv.py", line 824, in main symlink=options.symlink) File "C:\Python33\lib\site-packages\virtualenv.py", line 992, in create_environment install_wheel(to_install, py_executable, search_dirs) File "C:\Python33\lib\site-packages\virtualenv.py", line 960, in install_wheel 'PIP_NO_INDEX': '1' File "C:\Python33\lib\site-packages\virtualenv.py", line 902, in call_subprocess % (cmd_desc, proc.returncode)) OSError: Command [path redacted]\ENV\Scripts\python.exe -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip failed with error code 1 I've never seen this error before, and the stack trace doesn't make any sense to me. I can successfully import pip from a Python shell. Can anyone help me fix this?
Update The env installs successfully when I supply the --system-site-packages flag.
727
The Python "ModuleNotFoundError: No module named 'pip'" occurs when pip is not installed in our Python environment. To solve the error, install the module by running the python -m ensurepip --upgrade command on Linux or MacOS or py -m ensurepip --upgrade on Windows.
The most frequent source of this error is that you haven't installed pip explicitly with pip install pip . Alternatively, you may have different Python versions on your computer, and pip is not installed for the particular version you're using.
With the default settings, venv will install both pip and setuptools. Using pip is the recommended way to install packages in Python, and setuptools is a dependency for pip . Because installing other packages is the most common use case for Python virtual environments, you'll want to have access to pip .
While this error can come due to multiple reasons but in most of the cases you will see this error because of pip package not installed in your System. So to solve this kind of error, you need to simply install pip package from the default Repo.
Useful workaround from the Python bug ticket for anybody else with this issue:
virtualenv venv --no-setuptools Alternatively, downgrade to 3.3.3. This should be fixed properly in 3.3.5
53
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.
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
