-
-
Notifications
You must be signed in to change notification settings - Fork 33k
gh-101100: Fix reference warnings in c-api/init.rst
documenting PyGILState_STATE
#139572
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
will simply return ``NULL`` indicating that there was no prior thread state. | ||
.. seealso: | ||
.. seealso:: |
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.
hmm, this ought've been caught by sphinx-lint, cc @ezio-melotti @hugovk
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.
Open an issue at https://github.com/sphinx-contrib/sphinx-lint ?
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.
Thanks, the PyGILState_GetThisThreadState
change looks good. I'll leave the rest of this to the Sphinx wizards.
.. note:: | ||
This function does not account for :term:`thread states <thread state>` created | ||
by something other than :c:func:`PyGILState_Ensure` (such as :c:func:`PyThreadState_New`). |
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.
@ZeroIntensity: Is this change correct?
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.
I thought it was, above:
the PyGILState_GetThisThreadState change looks good.
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.
Oh, I didn't notice that @ZeroIntensity already reviewed the PR :-) So we're good :-)
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.
LGTM
Thanks @StanFromIreland for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…ng `PyGILState_STATE` (pythonGH-139572) (cherry picked from commit d2deb8f) Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
Sorry, @StanFromIreland and @hugovk, I could not cleanly backport this to
|
GH-139832 is a backport of this pull request to the 3.14 branch. |
…cumenting `PyGILState_STATE` (pythonGH-139572) (cherry picked from commit d2deb8f) Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
GH-139833 is a backport of this pull request to the 3.13 branch. |
PyGILState_STATE
: If we don't want to document, I can add it to the ignore list.I also fixed two
.. seealso::
blocks I noticed.📚 Documentation preview 📚: https://cpython-previews--139572.org.readthedocs.build/