[issue31321] traceback.clear_frames() doesn't clear *all* frames

Change by STINNER Victor : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue31321] traceback.clear_frames() doesn't clear *all* frames

STINNER Victor added the comment: See bpo-31323 where I wanted to use traceback.clear_frames() to manually break a reference cycle. -- ___ Python tracker ___ ___

[issue31321] traceback.clear_frames() doesn't clear *all* frames

Changes by STINNER Victor : -- versions: +Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue31321] traceback.clear_frames() doesn't clear *all* frames

Changes by STINNER Victor : Added file: http://bugs.python.org/file47116/clear_frames_bug.py ___ Python tracker ___ ___ Python-bugs-list maili

[issue31321] traceback.clear_frames() doesn't clear *all* frames

STINNER Victor added the comment: traceback.clear_frames() was added by bpo-1565525: commit 173a157e725579eec1f28f8c9d53d6761ba6c79f. -- ___ Python tracker ___ _

[issue31321] traceback.clear_frames() doesn't clear *all* frames

STINNER Victor added the comment: Would it be ok to backport such change to Python 3.6? It's a bugfix, no? -- ___ Python tracker ___ _

[issue31321] traceback.clear_frames() doesn't clear *all* frames

Changes by STINNER Victor : -- pull_requests: +3305 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue31321] traceback.clear_frames() doesn't clear *all* frames

New submission from STINNER Victor: traceback.clear_frames(): "Clears the local variables of all the stack frames in a traceback tb by calling the clear() method of each frame object." https://docs.python.org/dev/library/traceback.html#traceback.clear_frames That's wrong: it only calls frame.cl