-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
BLD: Define PyErr_SetFromWindowsErr on Cygwin. #23066
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
BLD: Define PyErr_SetFromWindowsErr on Cygwin. #23066
Conversation
This function is defined on Windows, not Cygwin. Should maybe request that upstream.
@DWesl just as curiosity, if you can build cpython from source yourself, can you check whether changing the ifdef at https://github.com/python/cpython/blob/39a54ba63850e081a4a5551a773df5b4d5b1d3cd/Include/pyerrors.h#L188 and https://github.com/python/cpython/blob/a4460f2eb8b9db46a9bce3c450c8b038038a7c93/Python/errors.c#L867 to also define these functions on cygwin works? Also, should the blocks protected by |
I didn't notice that PyErr_SetString returned void. This should return something normal.
It looks like enabling the Windows code in |
No hurries. |
It looks like it compiles, but it's a bit tricky to get useful test results with the system FreeType, rather than specifically FreeType 2.6.1 |
Is this still a work-in-progress? Moved to draft, but feel free to ask that it be moved back for active review... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This successfully fixes build on Cygwin; not sure there is anything else that really needs to be done.
…066-on-v3.5.x Backport PR #23066 on branch v3.5.x (BLD: Define PyErr_SetFromWindowsErr on Cygwin.)
PR Summary
Define
PyErr_SetFromWindowsErr
on Cygwin. This function is defined on Windows, not Cygwin.Closes #22997.
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).