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 izbyshev
Recipients gregory.p.smith, hroncok, izbyshev, nanjekyejoannah, pablogsal, torsava, vstinner
Date 2021-02-03.16:56:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> IMO the fix is simple: only create OSError from the errno, never pass a filename.

This will remove a normally helpful piece of the error message in exchange to being marginally less confusing in a rare case of non-existing interpreter (the user will still be left wondering why the file they tried to run exists, but "No such file or directory" is reported). So the only "win" here would be for CPython developers because users will be less likely to report a bug like this one.

> posix_spawn() is really complex function which can fail in many different ways.

This issue is not specific to posix_spawn(): subprocess and os.execve() report the filename too. Any fix would need to change those too for consistency.
Date User Action Args
2021-02-03 16:56:28izbyshevsetrecipients: + izbyshev, gregory.p.smith, vstinner, torsava, hroncok, pablogsal, nanjekyejoannah
2021-02-03 16:56:28izbyshevsetmessageid: <>
2021-02-03 16:56:28izbyshevlinkissue43113 messages
2021-02-03 16:56:28izbyshevcreate