This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients LewisGaul, miss-islington, nanjekyejoannah, nascheme, pablogsal, pitrou, tim.peters
Date 2020-08-16.19:56:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I suspect you're reading some specific technical meaning into the word "block" that the PR and release note didn't intend by their informal use of the word. But I'm unclear on what technical meaning you have in mind.

Before the change, gc "just gave up" after seeing a resurrection, ending the then-current cyclic gc run. It that sense, yes, resurrection "blocked" gc from making progress. It did not, e.g., "block" the interpreter in the sense of deadlock, or of waiting for some lock to be released, or of waiting for a network request to respond, or ...
Date User Action Args
2020-08-16 19:56:34tim.peterssetrecipients: + tim.peters, nascheme, pitrou, pablogsal, miss-islington, nanjekyejoannah, LewisGaul
2020-08-16 19:56:34tim.peterssetmessageid: <>
2020-08-16 19:56:34tim.peterslinkissue38379 messages
2020-08-16 19:56:34tim.peterscreate