| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Nearly there!
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Thanks @StanFromIreland for the PR, and @ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
Sorry, something went wrong.
(cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
|
GH-141549 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
(cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
|
GH-141550 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
The documentation doesn't mention that the function always returns 0 if called from a thread which is not the main thread, or an interpreter which is not the main interpreter. Only the main thread of the main interpreter can return 1. |
Sorry, something went wrong.
|
I thought about that, but I didn't think it was particularly important; it's technically an implementation detail, it's not too noticeable in practice, and most people should use PyErr_CheckSignals anyway. Feel free to submit a follow-up PR if you feel strongly about documenting that. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--141526.org.readthedocs.build/