Łukasz Langa added the comment:
I agree this should be fixed. Since we've already released 3.8.1 and 3.8.2 with
this behavior it's hard to justify blocking releases on this, though.
--
priority: release blocker -> high
___
Python tracker
Eric Snow added the comment:
I don't see a reason not to consider this is a regression.
The only problem with the fix would be for any users that rely on the
inaccurate reporting of the threading module. Considering that possibly
includes only some embedders (and folks using _thread module
Eric Snow added the comment:
Hmm, I wonder if this should be considered a regression in 3.8. As
demonstrated in issue38904, the following code changed behavior as of 3.8,
under certain conditions:
import signal
import threading
def int_handler():
...
if threading.current_thread() ==
New submission from Eric Snow :
The threading module has a "main_thread()" function that returns a Thread
instance for the "main" thread. The main thread is the one running when the
runtime is initialized and has a specific role in various parts of the runtime.
Currently the threading
