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 ncoghlan
Recipients eric.snow, ncoghlan, steve.dower
Date 2018-03-29.15:37:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm not sure what the right solution is at the design level, but I did recently run into a quirk related to this in the embedding tests: on \*nix systems, PySys_SetProgramName affects sys.executable, while Windows ignores it.

But certainly the intention is that a non-None sys.executable should be usable the way multiprocessing and the test suite use it: as a way to run Python in a subprocess. If an embedding environment wants to support that, it can set it to something suitable, and if it doesn't, it can set it to None.

(I do sometimes wonder if subprocess should have some sys.executable-specific helpers though - rerunning Python with the same settings as the current Python requires quite a bit more than just calling sys.executable with no particular options)
Date User Action Args
2018-03-29 15:37:46ncoghlansetrecipients: + ncoghlan, eric.snow, steve.dower
2018-03-29 15:37:45ncoghlansetmessageid: <>
2018-03-29 15:37:45ncoghlanlinkissue33180 messages
2018-03-29 15:37:45ncoghlancreate