[backport to 3.5] bpo-27122: Fix comment to point to correct issue number (#47) by berkerpeksag · Pull Request #50 · python/cpython
It took me quite a bit to figure out what this was referring to, since the given issue number is wrong, and the original commit message I found through git blame lists a different, also wrong issue number... see https://bugs.python.org/issue27122#msg279449 (cherry picked from commit af88e7e)
colesbury referenced this pull request in colesbury/nogil
Oct 6, 2021Once the threads object queue is empty, other threads may explicitly merge reference counts immediately. It's no longer safe for the original thread to do RC operations because of races with accesses to ob_ref_local. This ensures that the queue is empty when it's removed from the hashtable mapping thread-id to queue. There are still other RC operations that can happen during thread destruction, so the call to _Py_queue_destroy will probably need to be moved. See #50
colesbury referenced this pull request in colesbury/nogil
Oct 6, 2021A partially initialized thread may have an entry in the interpreter without a corresponding entry in the biased-refcounting hashtable. See #50
jaraco pushed a commit that referenced this pull request
Dec 2, 2022jaraco added a commit to jaraco/cpython that referenced this pull request
Feb 17, 2023This was referenced
Feb 11, 2025DinoV added a commit to DinoV/cpython that referenced this pull request
Jan 28, 2026This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters