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 brian.curtin
Recipients Christophe Simonis, Iztok.Kavkler, Omega_Weapon, ajaksu2, andybuckley, brian.curtin, christian.heimes, edemaine, eric.araujo, giampaolo.rodola, iki, loewis, meatballhat, michael.foord, pitrou, r.david.murray, sandro.tosi, schmir, sfllaw, tarek,, tmick, vstinner, weeble, wrstlprmpft
Date 2012-06-19.18:38:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Before we miss yet another beta freeze, how does something like this look? 

It moves `which` into one function which always yields paths. I don't think anyone will approve of adding a dual-function API to solve this problem. I originally tried an approach where the function returned one value and had an option to return an iterator, but nearly everyone I asked found it unacceptable and potentially confusing.

This patch removes the custom pathext stuff seen in other patches. It doesn't seem like it would be that useful to have it, and I'm not sure why you would want to.

Unless anyone is violently opposed, I think we should just go on with it. If we want to add to it, we can add to it in 3.4, but I think something should go in for 3.3. The issue has been open with various patches for over 10 years...
Date User Action Args
2012-06-19 18:38:11brian.curtinsetrecipients: + brian.curtin, loewis, tmick, edemaine, pitrou, vstinner, wrstlprmpft, giampaolo.rodola, christian.heimes, ajaksu2, sfllaw, schmir, tarek, eric.araujo, Christophe Simonis, andybuckley, weeble, r.david.murray,, michael.foord, meatballhat, sandro.tosi, iki, Iztok.Kavkler, Omega_Weapon
2012-06-19 18:38:10brian.curtinsetmessageid: <>
2012-06-19 18:38:09brian.curtinlinkissue444582 messages
2012-06-19 18:38:08brian.curtincreate