Message282050
| Author |
wolma |
| Recipients |
asvetlov, chris.jerdonek, cvrebert, docs@python, ned.deily, paul.moore, pepalogik, python-dev, steve.dower, tim.golden, wolma, zach.ware |
| Date |
2016年11月29日.22:26:10 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1480458370.87.0.464804467858.issue15533@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Just found issue15451, which reports a similar inconsistency between Windows and POSIX for 'PATH' provided through the Popen env parameter as for cwd. It seems that, on POSIX-platforms, the PATH environment variable passed through env affects the executable lookup if executable does *not* contain a dirname, but on Windows the new PATH never affects executable lookup. So, again, relative executable paths are causing platform-specific behavior. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年11月29日 22:26:11 | wolma | set | recipients:
+ wolma, paul.moore, tim.golden, ned.deily, cvrebert, asvetlov, chris.jerdonek, docs@python, python-dev, zach.ware, steve.dower, pepalogik |
| 2016年11月29日 22:26:10 | wolma | set | messageid: <1480458370.87.0.464804467858.issue15533@psf.upfronthosting.co.za> |
| 2016年11月29日 22:26:10 | wolma | link | issue15533 messages |
| 2016年11月29日 22:26:10 | wolma | create |
|