Stefan Krah <stefan-use...@bytereef.org> added the comment: Michael Haubenwallner <rep...@bugs.python.org> wrote: > @Stefan: Nope, setting some PATH in ~/.cshrc is the wrong thing to do, and it > actually is the reason for this issue at all: > 'which' is intended to tell the location of some command that would be used > when started on current commandline or within current running shell-script > using _current_ PATH. When ~/.cshrc modifies PATH, the found command-path > would be wrong (or not found at all).
Yes, that's why I wrote "in the worst case". Of course AIX 'which' is broken, but this could be easily fixed by IBM. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7742> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
