gh-141004: Document PyOS_InterruptOccurred#141526
Conversation
ZeroIntensity
added
needs backport to 3.13
|
Thanks @StanFromIreland for the PR, and @ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
(cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <[email protected]>
|
GH-141549 is a backport of this pull request to the 3.14 branch. |
(cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <[email protected]>
|
GH-141550 is a backport of this pull request to the 3.13 branch. |
…41549) gh-141004: Document `PyOS_InterruptOccurred` (GH-141526) (cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <[email protected]>
|
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. |
|
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 |
…41550) gh-141004: Document `PyOS_InterruptOccurred` (GH-141526) (cherry picked from commit ef90261) Co-authored-by: Stan Ulbrych <[email protected]>
3 participants
📚 Documentation preview 📚: https://cpython-previews--141526.org.readthedocs.build/