[issue20622] Python3.3 venv pip fails to run if path contains spaces
New submission from FeralBytes: Well trying to test out venv on Python 3.3.2 on Linux Mint 16 x64 I was not able to get pip to execute correctly after it had been installed. The error from bash is: (venv) wolfrage@wolfrage-KGP-M-E-D16 /media/ShareDrives/HomePlus/Jordan/Projects/The Strategist $ pip install pysdl2 bash: /home/wolfrage/Projects/The Strategist/venv/bin/pip: /home/wolfrage/Projects/The: bad interpreter: No such file or directory Same exact setup procedures in a path with out any spaces works as expected: (venv) wolfrage@wolfrage-KGP-M-E-D16 /media/ShareDrives/HomePlus/Jordan/Projects $ pip install pysdl2 --allow-external pysdl2 --allow-unverified pysdl2 Downloading/unpacking pysdl2 pysdl2 is potentially insecure and unverifiable. Downloading PySDL2-0.8.0.zip (1.1MB): 1.1MB downloaded Running setup.py (path:/media/ShareDrives/HomePlus/Jordan/Projects/venv/build/pysdl2/setup.py) egg_info for package pysdl2 Installing collected packages: pysdl2 Running setup.py install for pysdl2 Successfully installed pysdl2 Cleaning up... (venv) wolfrage@wolfrage-KGP-M-E-D16 /media/ShareDrives/HomePlus/Jordan/Projects $ python3 Python 3.3.2+ (default, Oct 9 2013, 14:50:09) [GCC 4.8.1] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sdl2 >>> exit() I hope that this can be fixed prior to 3.4 being released. This not only affected pip but easy_install too. -- components: Library (Lib) messages: 211193 nosy: FeralBytes priority: normal severity: normal status: open title: Python3.3 venv pip fails to run if path contains spaces type: behavior versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue20622> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20622] Python3.3 venv pip fails to run if path contains spaces
FeralBytes added the comment: Wow that is a very compelling argument that I am hesitant to raise a counter point against. But I feel I would at least like to understand better. So why does this issue not affect the interpreter in the venv itself, only pip and easy_install, or other such tools with-in the venv? It seems to me that the activate script gets around this somehow for the interpreter, as it ran fine in the directory with a space in the name. Is it possible to apply the same fix action to at least pip since it will be included in venv once 3.4 is final, for a better user experience, or at least less user complaints? In the meantime, I will fix my directory to use underscores instead of spaces. Thank you for your time. -- resolution: invalid -> status: pending -> open ___ Python tracker <http://bugs.python.org/issue20622> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
