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 r.david.murray
Recipients docs@python, loewis, mcmahon_m, r.david.murray, snaury, techtonik
Date 2010-07-03.15:08:27
SpamBayes Score 1.2208264e-05
Marked as misclassified No
Message-id <1278169709.98.0.292227363321.issue1576313@psf.upfronthosting.co.za>
In-reply-to
Content
The unix model should be followed (requiring an explicit reference to the current directory if it is not already in PATH), rather than the insecure Windows behavior, and this is indeed the current situation.  The current behavior is documented ("a full or relative path"), but a footnote that this differs from the msvcrt behavior would probably be a useful addition.  So I'm changing this to a doc bug.  (I have verified that ./ works, I have not verified the msvcrt behavior.)
History
Date User Action Args
2010-07-03 15:08:30r.david.murraysetrecipients: + r.david.murray, loewis, snaury, techtonik, mcmahon_m, docs@python
2010-07-03 15:08:29r.david.murraysetmessageid: <1278169709.98.0.292227363321.issue1576313@psf.upfronthosting.co.za>
2010-07-03 15:08:28r.david.murraylinkissue1576313 messages
2010-07-03 15:08:27r.david.murraycreate