Skip to content

Mismatch in description of PyThreadState_Delete and PyThreadState_DeleteCurrent #133989

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

Closed
AlexanderWells-diamond opened this issue May 14, 2025 · 2 comments
Labels
docs Documentation in the Doc dir topic-C-API

Comments

@AlexanderWells-diamond
Copy link

Documentation

It seems that the description for PyThreadState_Delete and PyThreadState_DeleteCurrent have a disagreement.

Under the _Delete method is the description: ...The global interpreter lock need not be held.

Under the _DeleteCurrent method is the description: Like PyThreadState_Delete, the global interpreter lock must be held

These two give different accounts of what the requirement is for the GIL.

@ZeroIntensity
Copy link
Member

This is already fixed on the 3.14 and 3.15 docs. I'm not sure it's a good idea to fix the documentation for all these functions on 3.13.

@AlexanderWells-diamond
Copy link
Author

Fair enough, if it's already fixed for future versions then I'm happy for this issue to be closed.

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 topic-C-API
Projects
Status: Todo
Development

No branches or pull requests

2 participants