This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients alexreg, ned.deily, ronaldoussoren, vinay.sajip, yan12125
Date 2016-12-27.15:19:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482851980.61.0.167133316421.issue28446@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-12-27 15:19:40vinay.sajipsetrecipients: + vinay.sajip, ronaldoussoren, ned.deily, alexreg, yan12125
2016-12-27 15:19:40vinay.sajipsetmessageid: <1482851980.61.0.167133316421.issue28446@psf.upfronthosting.co.za>
2016-12-27 15:19:40vinay.sajiplinkissue28446 messages
2016-12-27 15:19:40vinay.sajipcreate