Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Windows, Python 3.8: 'python -m pip install' pulls wrong version when run from VS command prompt #1609
Comments
Hard to say why pip thinks it's a 32-bit Python when Python is clearly a 64-bit interpreter, but this is definitely not the right bug tracker - this is for the python.org website, not for Python or pip. It wouldn't surprise me if you had a copy of pip in your |
Describe the bug
After downloading Python 3.8 for Win64 and installing locally, running it and asking it to use pip to install a package such as numpy gets the 32-bit version and not the 64-bit version.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The -m pip install line should install numpy-1.19.0-cp38-cp38-win_amd64.whl
Instead, it downloads and installs numpy-1.19.0-cp38-cp38-win32.whl
If you download numpy-1.19.0-cp38-cp38-win_amd64.whl by hand and use that filename instead of just 'numpy', it will refuse to install it:
Note that it is actually using the newly-installed version of pip: it will complain that I am using an outdated version of pip and suggest that I install the latest version, and when I do, it stops complaining.
The exact same commands work fine from a cygwin window or a 'cmd' window.
The same commands also work for Python 3.6 and 3.7 in a VS2019 command prompt: it is something Python 3.8-specific.
The text was updated successfully, but these errors were encountered: