Message179889
| Author |
takluyver |
| Recipients |
Christophe Simonis, Iztok.Kavkler, Omega_Weapon, ajaksu2, andybuckley, belopolsky, brian.curtin, christian.heimes, edemaine, eric.araujo, georg.brandl, giampaolo.rodola, iki, loewis, meatballhat, michael.foord, petere, pitrou, python-dev, r.david.murray, sandro.tosi, schmir, sfllaw, takluyver, tarek, tleeuwenburg@gmail.com, tmick, vstinner, weeble, wrstlprmpft |
| Date |
2013年01月13日.19:46:59 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1358106419.46.0.137279156902.issue444582@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The 'short circuit' appears to do what I'd consider the wrong thing when an executable file of the same name exists in the working directory. i.e. which('setup.py') can return 'setup.py', even though running 'setup.py' in a shell doesn't work (you need ./setup.py).
This is on UNIX-y systems, I see from the comments that the cwd is implicitly on the path in Windows.
Is this in scope for which() to deal with? Should I open a bug for it? Apologies if it's been discussed already. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年01月13日 19:46:59 | takluyver | set | recipients:
+ takluyver, loewis, tmick, georg.brandl, edemaine, belopolsky, pitrou, vstinner, wrstlprmpft, giampaolo.rodola, christian.heimes, ajaksu2, sfllaw, schmir, tarek, eric.araujo, Christophe Simonis, andybuckley, weeble, r.david.murray, tleeuwenburg@gmail.com, michael.foord, brian.curtin, meatballhat, petere, sandro.tosi, iki, Iztok.Kavkler, python-dev, Omega_Weapon |
| 2013年01月13日 19:46:59 | takluyver | set | messageid: <1358106419.46.0.137279156902.issue444582@psf.upfronthosting.co.za> |
| 2013年01月13日 19:46:59 | takluyver | link | issue444582 messages |
| 2013年01月13日 19:46:59 | takluyver | create |
|