Skip to content

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

Merged
merged 1 commit into from
Jul 29, 2021

Conversation

ammaraskar
Copy link
Member

@ammaraskar ammaraskar commented Apr 29, 2021

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

@bedevere-bot bedevere-bot added the docs Documentation in the Doc dir label Apr 29, 2021
@ammaraskar ammaraskar force-pushed the document_pyunicode_kind branch 2 times, most recently from e4a58d2 to 6f64245 Compare April 29, 2021 16:58
@ammaraskar ammaraskar changed the title bpo-43565: Document that PyUnicode_KIND's return as an enum bpo-43565: Document PyUnicode_KIND's return type as an enum Apr 29, 2021
@zware
Copy link
Member

zware commented Apr 29, 2021

This looks reasonable to me, but this is well outside of my comfort zone :). Maybe @vstinner or @methane could give this the OK?

@ammaraskar ammaraskar changed the title bpo-43565: Document PyUnicode_KIND's return type as an enum bpo-43565: Document PyUnicode_KIND's return type as an unsigned int Apr 29, 2021
@ammaraskar ammaraskar force-pushed the document_pyunicode_kind branch from 6f64245 to da9c628 Compare April 29, 2021 19:39
@github-actions
Copy link

github-actions bot commented Jun 3, 2021

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Jun 3, 2021
@encukou encukou added needs backport to 3.9 only security fixes needs backport to 3.10 only security fixes labels Jul 27, 2021
@encukou
Copy link
Member

encukou commented Jul 27, 2021

@ammaraskar, could you merge in the main branch to let the updated checks run?
I'll do it if you don't get to it in a while.

@ammaraskar
Copy link
Member Author

Sure thing, closing and re-opening the PR also re-runs the checks. Let me go ahead and do that.

@ammaraskar ammaraskar closed this Jul 27, 2021
@ammaraskar ammaraskar reopened this Jul 27, 2021
@encukou encukou merged commit 47fd472 into python:main Jul 29, 2021
@miss-islington
Copy link
Contributor

Thanks @ammaraskar for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.9.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-27439 is a backport of this pull request to the 3.10 branch.

@bedevere-bot
Copy link

GH-27440 is a backport of this pull request to the 3.9 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.9 only security fixes label Jul 29, 2021
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 29, 2021
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 29, 2021
encukou pushed a commit that referenced this pull request Jul 29, 2021
encukou pushed a commit that referenced this pull request Jul 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news stale Stale PR or inactive for long period of time.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants