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 jamesdlin
Recipients docs@python, jamesdlin, r.david.murray
Date 2017-07-02.00:38:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, but the Python docs have scary-looking warnings about using shell=True, so people (rightly) should avoid using shell=True if they don't think that they need it.  And in this case, people might not even know that they're invoking some binary that expects PWD from the shell.  

In my experience, it's not that uncommon for people to rewrite sh/bash shell scripts in Python.  Something starts off as a sh/bash script, evolves to a point where it's cumbersome to maintain, and it gets rewritten in Python.  But after it's rewritten, some invoked binaries might not behave as before, and it's unclear why.

When I encountered this problem myself, the first thing I tried was to explicitly set the `cwd` argument.  Some mention of the PWD environment variable would have saved me a lot of time.
Date User Action Args
2017-07-02 00:38:27jamesdlinsetrecipients: + jamesdlin, r.david.murray, docs@python
2017-07-02 00:38:27jamesdlinsetmessageid: <>
2017-07-02 00:38:27jamesdlinlinkissue30798 messages
2017-07-02 00:38:26jamesdlincreate