Message284107
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 Windows the Python launcher should honour spaces in the interpreter path.
Spaces in shebang lines are not supported where they're not supported by the underlying POSIX implementation - which includes Linux and OS X, AFAICT. |
|
Date |
User |
Action |
Args |
2016-12-27 15:19:40 | vinay.sajip | set | recipients:
+ vinay.sajip, ronaldoussoren, ned.deily, alexreg, yan12125 |
2016-12-27 15:19:40 | vinay.sajip | set | messageid: <1482851980.61.0.167133316421.issue28446@psf.upfronthosting.co.za> |
2016-12-27 15:19:40 | vinay.sajip | link | issue28446 messages |
2016-12-27 15:19:40 | vinay.sajip | create | |
|