On Thu, Jun 20, 2019 at 8:21 AM Michael Foord <firstname.lastname@example.org> wrote:
> It works by raising an exception in the target thread, which the thread is free to handle (usually for cleanup and then reraise).
Sure, those are the right semantics. How does it stop blocking I/O though? Suppose the thread is waiting for a server to return a response which just isn't ever going to come, but the connection somehow is kept open by the other side?
--Guido van Rossum (python.org/~guido)
Pronouns: he/him/his (why is my pronoun here?)