homepage

see http://starship.python.net/~tmick/#which
The author agrees with me in his README.
Even better: include which as a module in the standard 
library so it can be used programmatically and as::
 python -m which ...
or maybe::
 python -m os.which ...
cheers

Logged In: YES 
user_id=21627
The URL is now bad... Do you have a current location of the
file?
In any case, we cannot really replace it unless Trent
actively contributes it. So you have to pursudate Trent to
contribute it first.

Logged In: YES 
user_id=801589
Current location: http://trentm.com/projects/which/
About getting Trent to actively contribute, I'll cite the 
linked page:
 "I also would be happy to have this be a replacement for 
the which.py in the Python CVS tree at dist/src/Tools/
scripts/which.py which is Unix-specific and not usable as a 
module; and perhaps for inclusion in the stdlib."
So I do not think this will be a problem.
(No way of cc:ing someone for sf.net replies? I will try 
contacting him directly, cc:ing you.)
cheers

Logged In: YES 
user_id=21627
Can you please work with Trent on contributing it? Determine
whether it should be targeted for the standard library or
for Tools/scripts; if for the standard library, somebody
needs to provide documentation and test cases also (and
there should be an API review by potential users).

Logged In: YES 
user_id=34892
I'm happy to contribute this to the Python core. There are
some TODOs here that I think should be worked through:
http://trentm.com/projects/which/TODO.txt
I'll see if wrstlprmpft and I can get through those. Help
and opinions from others very welcome.

I think Tools/scripts/which.py is obsoleted by the upcoming shutil.which function.