Author pepalogik
Recipients asvetlov, chris.jerdonek, cvrebert, damon-atkins, docs@python, eryksun, ned.deily, paul.moore, pepalogik, python-dev, steve.dower, tim.golden, wolma, zach.ware
Date 2018-06-13.14:08:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528898911.22.0.947875510639.issue15533@psf.upfronthosting.co.za>
In-reply-to
Content
@eryksun: Sorry for my late reply, apparently I did not have time to reply in 2017. I see your point, but still I think that Python is conceptually multi-platform, so its behavior on Linux and Windows should be as much consistent as possible.

I am not the one to decide which one of the two possible behaviors shall be the correct one. The current documentation <https://docs.python.org/3/library/subprocess.html#subprocess.Popen> describes the behavior on Linux: "In particular, the function looks for executable (or for the first item in args) relative to cwd if the executable path is a relative path." If this is chosen as the correct behavior, then the behavior on Windows is incorrect.

@Damon Atkins: Thank you for reminding this issue, but I suspect your proposed solution of being thread-unsafe. I propose another solution: On Windows, Python should resolve the executable path itself (taking cwd and env into account) and then pass the absolute path to CreateProcess().
History
Date User Action Args
2018-06-13 14:08:31pepalogiksetrecipients: + pepalogik, paul.moore, tim.golden, ned.deily, cvrebert, asvetlov, chris.jerdonek, docs@python, python-dev, zach.ware, eryksun, steve.dower, wolma, damon-atkins
2018-06-13 14:08:31pepalogiksetmessageid: <1528898911.22.0.947875510639.issue15533@psf.upfronthosting.co.za>
2018-06-13 14:08:31pepalogiklinkissue15533 messages
2018-06-13 14:08:31pepalogikcreate