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 gregory.p.smith
Recipients asvetlov, chris.jerdonek, cvrebert, damon-atkins, docs@python, eryksun, gregory.p.smith, ned.deily, paul.moore, pepalogik, python-dev, steve.dower, tim.golden, wolma, zach.ware
Date 2021-03-17.01:56:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For our subprocess docs, Eryk's text:

For POSIX, ``executable`` should be stated as a "relative path without a slash in it" or a "relative path without a directory in it". An unqualified filename is a relative path that won't be resolved against ``cwd``, unless there's a "." entry in PATH.

For Windows, the use of CreateProcess() is documented. It could be stated more explicitly that ``executable``, ``args`` / ``list2cmdline(args)``, ``env``, and ``cwd`` are passed directly to CreateProcess() as lpApplicationName, lpCommandLine, lpEnvironment, and lpCurrentDirectory.

is quite reasonable.  I wouldn't include your long notes.  But a link to a MSDN article explaining that would be useful at the end of the Windows paragraph.

For the POSIX case we should describe which PATH is used.  The current one, or the one set in a ``env`` dict.
Date User Action Args
2021-03-17 01:56:51gregory.p.smithsetrecipients: + gregory.p.smith, paul.moore, tim.golden, ned.deily, cvrebert, asvetlov, chris.jerdonek, docs@python, python-dev, zach.ware, eryksun, steve.dower, pepalogik, wolma, damon-atkins
2021-03-17 01:56:51gregory.p.smithsetmessageid: <>
2021-03-17 01:56:51gregory.p.smithlinkissue15533 messages
2021-03-17 01:56:51gregory.p.smithcreate