René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[3.14] change in behaviour in gc.get_referrers(some_local)","articleBody":"# Bug report\r\n\r\n### Bug description:\r\n\r\n```python\r\nimport gc\r\n\r\nasync def demo():\r\n    class A:\r\n        pass\r\n\r\n    a = A()\r\n    print(gc.get_referrers(a))\r\n\r\n\r\ntry:\r\n    demo().send(None)\r\nexcept StopIteration as e:\r\n    print(f\"{e.value=}\")\r\n```\r\n\r\non 3.11-3.13 this prints:\r\n\r\n```\r\n[]\r\ne.value=None\r\n```\r\n\r\non 3.14 this prints:\r\n```\r\n[\u003ccoroutine object demo at 0x7d00fff85000\u003e]\r\ne.value=None\r\n```\r\n\r\nthis makes gc.get_referrers less useful in detecting cyclic garbage where I'd like to be able to make the assertion that the current frame is the only referrer to an Exception.\r\n\r\nthe alternative is to hold a weak reference to the object, delete the object and see if the weak reference is dead with the gc disabled. But then I don't get any debug information in my failing test of why the object is still alive.\r\n\r\n### CPython versions tested on:\r\n\r\n3.14, CPython main branch\r\n\r\n### Operating systems tested on:\r\n\r\nLinux\r\n\r\nnote: @markshannon asked me to open this issue\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-125640\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/graingert","@type":"Person","name":"graingert"},"datePublished":"2024-10-16T16:04:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/125603/cpython/issues/125603"}