Ctrl-C Does Not Do Anything While A Subinterpreter Is Running in the Main Thread #113130
Labels
3.12
bugs and security fixes
3.13
new features, bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
topic-subinterpreters
type-bug
An unexpected behavior, bug, or error


Bug report
This sort of makes sense since signals are handled by the main thread of the main interpreter, and only via the eval breaker (triggered exclusively in the eval loop). Thus if a subinterpreter is running in the main thread, signals (including from Ctrl-C) won't be handled until the next time the main interpreter is running in the main thread.
Possible solutions:
The text was updated successfully, but these errors were encountered: