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 ncoghlan
Recipients alex, cvrebert, eric.araujo, ncoghlan
Date 2011-10-21.23:02:53
SpamBayes Score 6.6343564e-10
Marked as misclassified No
Message-id <>
Initially, because I was suggesting the names shadow the subprocess convenience functions so they *had* to live in a different namespace.

However, even after changing the names to explicitly include "shell", I'd like to keep them away from the general subprocess functionality - these wrappers are more convenient for shell operations than the subprocess ones, but it's that very convenience that makes them potentially dangerous in larger applications that may be interpolating data that untrusted users can manipulate.

Since the intended audience is system administrators working on shell-like operations, the shell utility module seems like an appropriate place for them. Both the "import shutil" and the "shell" in the names would then serve as red flags on a code review or security audit.
Date User Action Args
2011-10-21 23:02:54ncoghlansetrecipients: + ncoghlan, eric.araujo, alex, cvrebert
2011-10-21 23:02:54ncoghlansetmessageid: <>
2011-10-21 23:02:53ncoghlanlinkissue13238 messages
2011-10-21 23:02:53ncoghlancreate