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 jwilk
Recipients dhduvall, gvanrossum, jbeck, jwilk, martin.panter, swalker
Date 2017-12-07.16:37:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512664649.16.0.213398074469.issue26414@psf.upfronthosting.co.za>
In-reply-to
Content
Linux man page for execvp(3)
<http://man7.org/linux/man-pages/man3/execvp.3.html> says:

> The default search path (used when the environment does not contain
> the variable PATH) shows some variation across systems.  It generally
> includes /bin and /usr/bin (in that order) and may also include the
> current working directory.  On some other systems, the current
> working is included after /bin and /usr/bin, as an anti-Trojan-horse
> measure.  The glibc implementation long followed the traditional
> default where the current working directory is included at the start
> of the search path.  However, some code refactoring during the
> development of glibc 2.24 caused the current working directory to be
> dropped altogether from the default search path.  This accidental
> behavior change is considered mildly beneficial, and won't be
> reverted.

So while having cwd is os.defpath has some historical justification,
now that glibc dropped it from its default PATH, it would be prudent for
Python to follow the suit.
History
Date User Action Args
2017-12-07 16:37:29jwilksetrecipients: + jwilk, gvanrossum, dhduvall, swalker, martin.panter, jbeck
2017-12-07 16:37:29jwilksetmessageid: <1512664649.16.0.213398074469.issue26414@psf.upfronthosting.co.za>
2017-12-07 16:37:29jwilklinkissue26414 messages
2017-12-07 16:37:29jwilkcreate