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.smith, eryksun, paul.moore, steve.dower, tim.golden, uranusjr, zach.ware
Date 2019-11-25.18:58:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yeah, this definitely relates to how Windows handles unqualified argv[0] in CreateProcess. Though I thought we checked that out in another issue and decided that "most" people are correctly using sys.executable here? (Or decided that it was documented well enough that they should, and using a "python" literal was relying on OS behaviour.)

I'm not a fan of trying to override the OS handling in subprocess, though that would be the fix. Possibly we could handle "python[.exe]" literals by substituting sys.executable transparently?
Date User Action Args
2019-11-25 18:58:07steve.dowersetrecipients: + steve.dower, paul.moore, eric.smith, tim.golden, zach.ware, eryksun, uranusjr
2019-11-25 18:58:07steve.dowersetmessageid: <>
2019-11-25 18:58:07steve.dowerlinkissue38905 messages
2019-11-25 18:58:07steve.dowercreate