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.

作者 andybuckley
收信人 Christophe Simonis, ajaksu2, andybuckley, brian.curtin, christian.heimes, edemaine, eric.araujo, iki, meatballhat, tarek, tleeuwenburg@gmail.com
日期 2010-07-08.17:08:36
SpamBayes Score 0.030990716
Marked as misclassified
Message-id <1278608919.18.0.184939810438.issue444582@psf.upfronthosting.co.za>
In-reply-to
内容
Personally I think it's a very useful feature: the purpose for running which may not be to get the full path to the executable and then run it, but rather that that path prefix is important for something else. I'm sure when I joined this issue I had some need like that -- after all, as you say, if you just want to run it then there are better ways.

In general, once users have a need (for whatever reason) to start firing off subprocesses from their Python scripts, things can get ugly. Providing a portable path search function provides a way to keep one kind of that ugliness inside Python for the cases where it really is needed. As for abuse... well, people will always find a way to abuse bits of the library: I think that's an issue for them, rather than a reason to block this functionality ;)

My $0.02,
Andy
历史
日期 用户 动作 参数
2010-07-08 17:08:39andybuckley修改recipients: + andybuckley, edemaine, christian.heimes, ajaksu2, tarek, eric.araujo, Christophe Simonis, tleeuwenburg@gmail.com, brian.curtin, meatballhat, iki
2010-07-08 17:08:39andybuckley修改messageid: <1278608919.18.0.184939810438.issue444582@psf.upfronthosting.co.za>
2010-07-08 17:08:36andybuckley链接issue444582 messages
2010-07-08 17:08:36andybuckley创建