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 andybuckley
Recipients Christophe Simonis, ajaksu2, andybuckley, brian.curtin, christian.heimes, edemaine, eric.araujo, iki, meatballhat, tarek,
Date 2010-07-08.17:08:36
SpamBayes Score 0.0309907
Marked as misclassified No
Message-id <>
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,
Date User Action Args
2010-07-08 17:08:39andybuckleysetrecipients: + andybuckley, edemaine, christian.heimes, ajaksu2, tarek, eric.araujo, Christophe Simonis,, brian.curtin, meatballhat, iki
2010-07-08 17:08:39andybuckleysetmessageid: <>
2010-07-08 17:08:36andybuckleylinkissue444582 messages
2010-07-08 17:08:36andybuckleycreate