[issue28446] pyvenv generates malformed hashbangs for scripts

2016-12-27 Thread Vinay Sajip
Vinay Sajip added the comment: As an extra data point, note the behaviour on Windows: C:\Users\Vinay> \python34\python -m venv "\Temp\aaa bbb"

[issue28446] pyvenv generates malformed hashbangs for scripts

2016-12-27 Thread Vinay Sajip
Vinay Sajip added the comment: To reiterate Alex Regueiro's point, I don't think this is a bug, but a shortcoming of the underlying Berkeley exec(2) implementation. See this post: https://lists.gnu.org/archive/html/bug-bash/2008-05/msg00053.html We can leave the implementation as is, as on Win

[issue28446] pyvenv generates malformed hashbangs for scripts

2016-12-16 Thread Chi Hsuan Yen
Chi Hsuan Yen added the comment: Seems there are quite a few typos/copy-paste errors in the original steps-to-reproduce. Here are my steps on macOS: $ ./python-build/python.exe -m venv 'aaa bbb' $ source ./aaa\ bbb/bin/activate $ pip zsh: /Users/yen/tmp/aaa bbb/bin/pip: bad interpreter: "/Users

[issue28446] pyvenv generates malformed hashbangs for scripts

2016-10-14 Thread Alex Regueiro
New submission from Alex Regueiro: Quotes around hashbangs are not recognised and are considered invalid syntax, at least on Bash on OS X 10.12. There's really no workaround (that I'm aware of) for paths containing spaces, except maybe symlinking the directory in the path the contains the spac