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-22.19:38:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Attached is a patch which fixes your review comments in Lib/, and it makes an adjustment in the wording of the documentation.

The documentation is a bit more strong in wording that the current directory is always prepended to the path whether its a provided path or the default value. I don't know that the PATHEXT mentions should go much further than saying that it's checked, and then showing what it does by example.

We always need to check the PATHEXT variable because it tells us what the accepted executable extensions are that the system will recognize. On my system, it's ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.RB;.RBW", so the command prompt allows me to type "python" and it'll search that list, search the path, and find "python.exe" at C:\Python33. It's something we need to check no matter what the `path` situation is, default or passed in.
Date User Action Args
2012-06-22 19:38:56brian.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-22 19:38:55brian.curtinsetmessageid: <>
2012-06-22 19:38:54brian.curtinlinkissue444582 messages
2012-06-22 19:38:54brian.curtincreate