Gregory P. Smith <g...@krypto.org> added the comment:
The irony... Documenting the caveat at least seems useful. Your workaround sounds reasonable. I don't love the idea of implementing our own mask blocked/unblocked state check, though it probably wouldn't be very complicated. Might be interesting. Another trick that'd "work" so long as people don't have multiple SIG_BLOCK calls (not something to depend on) is to force a check of our interpreter signal flags right before signal.pthread_sigmask returns to the Python caller. ---------- nosy: +gregory.p.smith stage: -> needs patch type: -> behavior versions: +Python 3.11 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue47139> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
