-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-43565: Document PyUnicode_KIND's return type as an unsigned int #25724
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
Conversation
e4a58d2
to
6f64245
Compare
6f64245
to
da9c628
Compare
This PR is stale because it has been open for 30 days with no activity. |
@ammaraskar, could you merge in the main branch to let the updated checks run? |
Sure thing, closing and re-opening the PR also re-runs the checks. Let me go ahead and do that. |
Thanks @ammaraskar for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.9. |
GH-27439 is a backport of this pull request to the 3.10 branch. |
GH-27440 is a backport of this pull request to the 3.9 branch. |
…ythonGH-25724) (cherry picked from commit 47fd472) Co-authored-by: Ammar Askar <[email protected]>
…ythonGH-25724) (cherry picked from commit 47fd472) Co-authored-by: Ammar Askar <[email protected]>
…H-25724) (GH-27439) (cherry picked from commit 47fd472) Co-authored-by: Ammar Askar <[email protected]>
…H-25724) (GH-27440) (cherry picked from commit 47fd472) Co-authored-by: Ammar Askar <[email protected]>
It looks like people are already using this enum within their code: https://github.com/search?p=1&q=enum+PyUnicode_Kind&type=Code
So as the bpo ticket suggests, we may as well document this type properly as an enum and correct the return type for
PyUnicode_KIND
https://bugs.python.org/issue43565