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 Olivier.Grisel
Recipients Olivier.Grisel, brett.cannon, eric.snow, ncoghlan, pitrou, python-dev, sbt
Date 2013-12-13.17:40:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386956431.37.0.157915392304.issue19946@psf.upfronthosting.co.za>
In-reply-to
Content
> The semantics are not going to change in python 3.4 and will just stay as they were in Python 3.3.

Well the semantics do change: in Python 3.3 the spawn and forkserver modes did not exist at all. The "spawn" mode existed but only implicitly and only under Windows.

So Python 3.4 is introducing a new feature for POSIX systems that will only work in the rare cases where the Python program is launched by a ".py" ending script.

Would running the `imp.load_source` trick only if `sys.platform != "win32"` be a viable way to preserve the semantics of Python 3.3 under the windows while not introducing a partially broken feature in Python 3.4?
History
Date User Action Args
2013-12-13 17:40:31Olivier.Griselsetrecipients: + Olivier.Grisel, brett.cannon, ncoghlan, pitrou, python-dev, sbt, eric.snow
2013-12-13 17:40:31Olivier.Griselsetmessageid: <1386956431.37.0.157915392304.issue19946@psf.upfronthosting.co.za>
2013-12-13 17:40:31Olivier.Grisellinkissue19946 messages
2013-12-13 17:40:31Olivier.Griselcreate