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 eric.araujo
Recipients dstufft, eric.araujo, eryksun, tbpassin, vstinner
Date 2020-01-09.01:45:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578534304.72.0.750763393728.issue39260@roundup.psfhosted.org>
In-reply-to
Content
The problem is that distutils.spawn.find_executable is an internal API, never meant for general usage.

Only minimal change happens to distutils these days, partly because the codebase is full of dark corners and weird interactions (so a fix can easily break someone else’s setup.py script), partly because few core developers have the expertise and willingess to write patches or review PRs.

So the question is: is the problem you reported a problem that happens when people write setup.py scripts, or when using the function for something else?  If it’s the latter, I’m afraid the safe course of action would be to change nothing, and recommend people use truly general-use functions like shutil.which.
History
Date User Action Args
2020-01-09 01:45:04eric.araujosetrecipients: + eric.araujo, vstinner, eryksun, dstufft, tbpassin
2020-01-09 01:45:04eric.araujosetmessageid: <1578534304.72.0.750763393728.issue39260@roundup.psfhosted.org>
2020-01-09 01:45:04eric.araujolinkissue39260 messages
2020-01-09 01:45:04eric.araujocreate