[issue31516] current_thread() becomes "dummy" thread during shutdown

miss-islington added the comment: New changeset d918e98056b7ef8d90d71805531cec3e67b5450e by Miss Islington (bot) in branch '3.6': bpo-31516: Skip test_main_thread_during_shutdown() with COUNT_ALLOCS builds. (GH-8052)

[issue31516] current_thread() becomes "dummy" thread during shutdown

miss-islington added the comment: New changeset c327a5499fa823f627366c17e20687065fd70449 by Miss Islington (bot) in branch '3.7': bpo-31516: Skip test_main_thread_during_shutdown() with COUNT_ALLOCS builds. (GH-8052)

[issue31516] current_thread() becomes "dummy" thread during shutdown

Change by miss-islington : -- pull_requests: +9192 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31516] current_thread() becomes "dummy" thread during shutdown

Change by miss-islington : -- pull_requests: +9191 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31516] current_thread() becomes "dummy" thread during shutdown

Serhiy Storchaka added the comment: New changeset 65d2f8c044bf597685ba72f66cbcc6b3f7a3ee9c by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-31516: Skip test_main_thread_during_shutdown() with COUNT_ALLOCS builds. (GH-8052)

[issue31516] current_thread() becomes "dummy" thread during shutdown

Change by Zackery Spytz : -- pull_requests: +7660 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: I have now pushed the fix to master and 3.6. Hopefully this won't break anyone's code... -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: New changeset ac6245a31f9a757db0520722c592cb7fdcb55eb0 by Antoine Pitrou (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31516: current_thread() should not return a dummy thread at shutdown (GH-3673) (#3856)

[issue31516] current_thread() becomes "dummy" thread during shutdown

Change by Roundup Robot : -- pull_requests: +3836 ___ Python tracker ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: New changeset 1023dbbcb7f05e76053486ae7ef7f73b4cdc5398 by Antoine Pitrou in branch 'master': bpo-31516: current_thread() should not return a dummy thread at shutdown (#3673)

[issue31516] current_thread() becomes "dummy" thread during shutdown

Tim Peters added the comment: Ya, it's clearly best for `current_thread()` to deliver consistent results. -- ___ Python tracker ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: Tim, any opinion on this one? Do you agree it's an actual bug (if a bit obscure)? -- ___ Python tracker ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Changes by Antoine Pitrou : -- keywords: +patch pull_requests: +3662 stage: needs patch -> patch review ___ Python tracker ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

[issue31516] current_thread() becomes "dummy" thread during shutdown

Antoine Pitrou added the comment: The main thread being marked "stopped" at shutdown might be an obscure feature (as hinted in the comments for threading._shutdown()). However, current_thread() should definitely not return a separate DummyThread instance. --

[issue31516] current_thread() becomes "dummy" thread during shutdown

New submission from Antoine Pitrou: Attaching reproducer. During interpreter shutdown, threading.main_thread() gets marked "stopped" (while it's obviously still running), while threading.current_thread() returns a DummyThread instance with the same ident as the main thread. $ ./python