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 steve.dower
Recipients eric.snow, ncoghlan, steve.dower
Date 2018-03-29.14:53:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If you host Python in another program, it's likely that sys.executable is not pointing to a normal Python interpreter. This can cause libraries such as multiprocessing to fail when they try to launch the interpreter again. Worse, it may have launched your application many more times before failure :)

I think we should add either a flag to indicate to any such library that sys.executable is not useful for relaunching Python, or a field that points to the actual executable but can safely be left None (or for most horrendous generality, a list of arguments to relaunch, as sometimes a command line option can get you into a normal interpreter). These would be set by embedders only, and Programs/python.c would set the "normal" values.

Date User Action Args
2018-03-29 14:53:31steve.dowersetrecipients: + steve.dower, ncoghlan, eric.snow
2018-03-29 14:53:31steve.dowersetmessageid: <>
2018-03-29 14:53:31steve.dowerlinkissue33180 messages
2018-03-29 14:53:31steve.dowercreate