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 Jurko.Gospodnetić
Recipients Benedek Rácz, Jurko.Gospodnetić, eric.smith, eryksun, paul.moore, steve.dower, tim.golden, uranusjr, zach.ware
Date 2020-06-03.11:09:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
encountered what I believe is the same problem, so here are some more details I noticed, after checking what exactly that process name lookup does using ProcessMonitor:

- when running my external process in a `venv` generated virtual environment, POpen() started subprocess executables are first looked up in the base Python executable's folder (the one used to create our virtual environment) as opposed to the one running the external Python process, if POpen() is called with `shell=False`

- when doing the same and passing `shell=True` to the POpen() call, there is no such initial folder in the lookup

- when doing the same on a `virtualenv` generated virtual environment, the file lookup is done in the correct folder first - the one containing the current Python executable and not in the base one
Date User Action Args
2020-06-03 11:09:05Jurko.Gospodnetićsetrecipients: + Jurko.Gospodnetić, paul.moore, eric.smith, tim.golden, zach.ware, eryksun, steve.dower, uranusjr, Benedek Rácz
2020-06-03 11:09:05Jurko.Gospodnetićsetmessageid: <>
2020-06-03 11:09:05Jurko.Gospodnetićlinkissue38905 messages
2020-06-03 11:09:05Jurko.Gospodnetićcreate