GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — [3.14] change in behaviour in gc.get_referrers(some_local) · Issue #125603 · python/cpython Open Labels 3.14bugs and security fixesbugs and security fixestriagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error DescriptionBug reportBug description:import gc async def demo(): class A: pass a = A() print(gc.get_referrers(a)) try: demo().send(None) except StopIteration as e: print(f"{e.value=}") on 3.11-3.13 this prints: on 3.14 this prints: this 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. the 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. CPython versions tested on:3.14, CPython main branch Operating systems tested on:Linux note: @markshannon asked me to open this issue Linked PRsActivity
MetadataMetadataAssigneesLabels3.14bugs and security fixesbugs and security fixestriagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error ProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |