PythonĢ.7.9 includes several significant changes unprecedented in a "bugfix" release: Python 2.7.9 is a bugfix version for the Python 2.7 release series. The entirety of Python 3.4's ssl module has been backported for Python Python 2.7.9 will include several significant changes I do not know what setuptools plans on with regards to distlib sorry.Īs 2.7 is now out of support, I'm going to go ahead and close this issue.Python 2.7.9rc1 is the first release candidate for the next bugfix version of For example:Ĭ:\>"C:\Program Files\Python27\Scripts\test.exe"Ĭ:\Program Files\Python27\Scripts\test-script.py So test.exe will actually run C:\program.exe, if it exists. Instead of errnously double quoting the EXE path, it doesn't quote it at all. Will setuptools eventually switch to using distlib also? Currently setuptools has a different problem. > it's own console scripts when installing from sdist too). > get fixed in setuptools (or pip will need to start writing > If the same problem exists in setuptools then it'll need to If the same problem exists in setuptools then it'll need to get fixed in setuptools (or pip will need to start writing it's own console scripts when installing from sdist too). If distlib 0.2.0 fixes this, then it should be fixed in pip 6+ when installing from Wheels. > On Dec 27, 2014, at 9:49 AM, Steve Dower wrote:
Install pythong 2.7.9 windows#
> the normal place on windows until this is fixed. exe, pip itself breaks on the same problem.
Install pythong 2.7.9 install#
> Having pip not work after a straight install to the normal place you'd install it on windows can't be a feature. On Dec 27, 2014, at 4:04 PM, Joshua Ellinger wrote: Which it can be correct to spawn a process in Windows where the path is quoted.
The safest fix would be to make subprocess strip double-quotes from the executable path.ĭouble quote (") is not an allowed character in Windows file systems. I don't have the link handy from my phone, but if you find the issue on bitbucket you can help attract some more attention to this. > I've previously reported this issue against setuptools (which generates the executable) and apparently they consider it a "feature". On Dec 27, 2014, at 9:49 AM, Steve Dower wrote: The normal place on windows until this is fixed. Having pip not work after a straight install to the normal place you'd install it on windows can't be a feature.Įven after I changed the. Pip 6.0.3 from C:\Program Files\Python27\lib\site-packages (python 2.7)
Install pythong 2.7.9 update#
The latest pip uses distlib 0.2.0, so just update from pip 1.5.6 to 6.0.3.Ĭ:\>"C:\Program Files\Python27\Scripts\pip.exe" -version I've previously reported this issue against setuptools (which generates the executable) and apparently they consider it a "feature". That should be the default in the installer if possible. Ps - Windows programs are normally installed under c:\Program Files or c:\Program Files (x86). I 'solved' by editing the pip.exe to remove the quotes.
The launcher does not remove the extra quotes and fails. The problem is that the python path name is quoted if it contains spaces. Pip.exe breaks if python 2.7.9 is installed under c:\Program Files\Pythonĭstufft, eryksun, joshuaellinger, steve.dower, tim.golden, zach.wareĬreated on 15:10 by joshuaellinger, last changed 06:11 by zach.ware.
0 kommentar(er)
