[issue34608] gc.get_referrers behavior change 3.6 to 3.7

INADA Naoki added the comment: Benjamin is right. This is very implementation detail. We shouldn't rely on such edge case. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue34608] gc.get_referrers behavior change 3.6 to 3.7

Change by Xiang Zhang : -- nosy: +inada.naoki, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue34608] gc.get_referrers behavior change 3.6 to 3.7

Benjamin Peterson added the comment: Likely fallout from 5a625d0aa6a6d9ec6574ee8344b41d63dcb9897e. get_referrers() doesn't really guarantee anything. It's more of a clever hack based on however the Python GC works at the moment. So, this it probably WONTFIX. -- nosy: +benjamin.peter

[issue34608] gc.get_referrers behavior change 3.6 to 3.7

New submission from Bryan : When called on a local object inside a function, gc.get_referrers no longer returns a Frame as one of the references. I could not find anything in the release notes or changeling that indicated that this is an intentional change. The following script generates diff