-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
distutils.command.build_ext raises FileNotFoundError #85379
Comments
In pypa/setuptools#2228, by adopting the distutils codebase from a late release of CPython, Setuptools stumbled onto an API-breaking change in distutils rooted at bpo-39763. Details are in the Setuptools investigation, but to summarize:
Setuptools discovered this behavior in the 48.0 release when it incorporated these distutils changes into a vendored release of Setuptools, but the failures exhibited will apply to all builds (including pyyaml) on Python 3.9. |
In pypa/distutils@7aa5abeafc, I've pushed a fix (with a repro test in the parent commit). I recommend this fix be applied to CPython 3.9. |
CPython should also consider this change, which unifies the |
Good catch! The unification change is 3.10 only but I'm totally fine accepting the _compile fix in Python 3.9. |
Do you mean mean that spawn() of distutils.spawn should catch FileNotFoundError and raise a CompilerError instead? It seems like before my commit 1ec63b6, any OSError was catched and replaced with DistutilsExecError, not only FileNotFoundError. Do you want to propose a fix? |
Sure. I'll submit patches. |
I learned the magical incantation to port commits from pypa/distutils to CPython:
|
I close the issue since it's fixed. I also reset the priority. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: