-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add compatibility to Py_T_* #125
Comments
Why do you test for Python 3.9?
The |
I didn't really investigate which version they came from. Maybe I'll look for them later.
Right. But I don't know what happened, sometimes it appears to be redefined. For this issue, WDYT? Edit e.g.
my change
|
But it is redefined on the premise that I change my current python version. But I hope it can be built successfully in most versions. |
On which Python version? |
My current version it is |
I don't see the purpose of this code. |
I wrote #126 to add these constants. Can you test my PR? |
I tested it and left a comment in your PR and the issue seems to be ok to be marked as resolved, but I need to wait for it to be merged into main. |
Fixed by 7eb512b. |
Hello Python team, I believe we have met countless times in the main repository.
When I port libfdt to Python, I noticed the
Py_T_*
series of macros, which are only available after version 3.12. Prior to this, theT_*
series was used. Can we add compatibility for these basic constants in a compatibility layer, so they are always defined asPy_T_*
in supported versions?If they are defined elsewhere, please point out my mistakes. Thank you, everyone :)
From my repo
(If the request is granted, I hope to complete this historic moment.)
The text was updated successfully, but these errors were encountered: