When using Python 3.10 on Windows, pip install --user installs scripts to wrong dir
See original GitHub issue- Git clone of ue4-docker
- Windows
- Python 3.10
- Run
pip install -e . --user
in ue4-docker repo root
Expected: ue4-docker.exe
script is installed in C:\Users\<user>\AppData\Roaming\Python\Python310\Scripts
.
Actual: ue4-docker.exe
script is installed in C:\Users\<user>\AppData\Roaming\Python\Python31\Scripts
.
Python310 != Python31.
Issue Analytics
- State:
- Created a year ago
- Comments:9
Top Results From Across the Web
pip giving error when trying to install packages Python 3.10
This error shows up on windows when one tries to use pip in the command prompt. To solve this error on windows, you...
Read more >Pip installing off PATH: should I do something? - Python Help
WARNING: The script tabulate.exe is installed in 'C:\Users\atomi\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\ ...
Read more >python >= 3.10 script directory (pip bin dir) should be minor ...
When installing python libraries with pip , they end up in /usr/local/lib/python3.10/site-packages/ (for example), so a directory that is stable ...
Read more >How to Install Pip on Windows - ActiveState
Open up the Control Panel and navigate to System and Security -> System; Click on the Advanced system settings link on the left...
Read more >Pip Command Not Found on Windows: A Guide | Built In
A “pip: command not found” error occurs when you haven't properly installed the package installer for Python (pip) on your computer.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah! I think I got it: https://github.com/pypa/setuptools/issues/3001. Looks like setuptools v60.4.0 fixed it via https://github.com/pypa/setuptools/pull/2953. Although again, this bug should also have affected the site-pacakges, not just the scripts.
But I’d definitely suggest upgrading setuptools and see if that fixes it.
Yeah, definitely this. From what I traced before,
{py_version_nodot}
is the name being used in the path in that version (later replaced with{py_version_nodot_plat}
seen above), and it was previously defined asi.e.
and is now
And before the above fix, this calculation hadn’t been touched since 2013.
I was on Python 3.10.2. I’ve just upgraded, and will try again. I’d suggest upgrading setuptools as well, perhaps.
The other thing I’d suggest is maybe try the Python installer directly, without Chocolatey? I had a quick look and nothing in the install scripts jumped out at me as “This will affect the user base dir”, but I’m running out of differences.
I just tried again after upgrading to Python 3.10.4, and it still works for me.
From the log:
So it’s clearly handing off to setuptools for the relevant step. You might find you can run
setup.py develop
directly and see what it does.Full log