OS: Windows 7, 64-bit
Python: 3.6.2 (64-bit)
pip: 10.0.0b2
I got a warning that I was not installing to a location on PATH
:
>pip install --force-reinstall wheel
Collecting wheel
Using cached wheel-0.31.0-py2.py3-none-any.whl
Installing collected packages: wheel
Found existing installation: wheel 0.31.0
Uninstalling wheel-0.31.0:
Successfully uninstalled wheel-0.31.0
The script wheel.exe is installed in 'c:\users\uk03306\appdata\local\programs\python\python36\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
However, C:\Users\UK03306\AppData\Local\Programs\Python\Python36\Scripts
is on PATH
:
>$env:PATH -split ';'
C:\Program Files\ConEmu\ConEmu\Scripts
C:\Program Files\ConEmu
C:\Program Files\ConEmu\ConEmu
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\ProgramData\Oracle\Java\javapath
C:\Utils\Gnuwin64
C:\Utils\Vim
C:\Utils\Misc
C:\Utils\SysInternals
C:\Program Files\TortoiseHg\
C:\Oracle\XE\app\oracle\product\11.2.0\server\bin
C:\Apps\Vagrant\bin
C:\Apps\Go\bin
C:\ProgramData\chocolatey\bin
C:\Users\UK03306\.dnx\bin
C:\Program Files\Microsoft DNX\Dnvm\
C:\Program Files\Microsoft SQL Server\130\Tools\Binn\
C:\Program Files\nodejs\
C:\Users\UK03306\AppData\Local\Programs\Git\cmd
C:\PostgreSQL\pg96\bin
C:\Program Files (x86)\Plantronics\Spokes3G\
C:\Program Files\dotnet\
C:\Users\UK03306\.cargo\bin
C:\Users\UK03306\.local\bin
C:\Users\UK03306\AppData\Local\Programs\Python\Python36\Scripts\
C:\Users\UK03306\AppData\Local\Programs\Python\Python36\
C:\Users\UK03306\AppData\Local\Programs\Git\cmd
C:\Users\UK03306\AppData\Roaming\npm
C:\Program Files\Docker Toolbox
C:\Program Files\Heroku\bin
C:\Program Files\Microsoft VS Code\bin
and the wheel command works fine:
>wheel version
wheel 0.31.0
I know the reported path doesn't match in case with the one on PATH
, so this may be a case sensitivity issue. But I had a previous run (with the dev version of pip) fail with a reported path that matched the entry in PATH
with the same case, so the problem may be deeper than that.
I'm gonna say we're missing an os.path.normcase somewhere. I think this is a release blocker, windows only though. I'll look into fixing it tonight or tomorrow morning.
I agree, it's likely something like that. I was going to take a look over the weekend, so if you don't get time I'll pick it up.
Not sure it's a release blocker - it's only cosmetic. But with luck that isn't a decision I'll need to make :-) So leave it that way for now, I can drop the tag later if needs be.
Fixed in #5180
In what version is it supposed to be fixed? I have pip 10.0.1 on Windows 7 x64 and it's showing me the same warning even though I have exactly the same directory in my PATH
system environment variable. Even the case is the same. The only difference is that the path in the environment variable ends with a slash and the directory reported by pip does not:
c:\development\python3\Scripts\
c:\development\python3\Scripts
I have modified the environment variable and removed the trailing slash but I cannot it test now.
That bug fix is a part of 18.0 - it should be releasing early next week. :)
@pradyunsg I just would like to note that I was describing a bit different issue - in my case, it wasn't caused by a different letter case but by a path with a trailing slash in the PATH
environment variable. Pip should normalize paths before checking them (in an addition to normalizing the case).
Has it been also addressed or should I take a look?
It's been addressed too along with this in 18.0.
@pradyunsg Are you sure? I don't see it has been addressed in the pull request. Or was it fixed anywhere else?
@ferenczy Yep. :)
This was addressed separately in #5293.
I see. Good :) Thank you.
The script virtualenv.exe is installed in 'c:python27\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.