[issue1441] Cycles through ob_type aren't freed

Changes by Benjamin Peterson : -- resolution: -> duplicate status: open -> closed superseder: -> __dict__ = self in subclass of dict causes a memory leak? ___ Python tracker ___

[issue1441] Cycles through ob_type aren't freed

Adam Olsen added the comment: As far as I know. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1441] Cycles through ob_type aren't freed

Mark Lawrence added the comment: Is this still valid? -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue1441] Cycles through ob_type aren't freed

Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mai

[issue1441] Cycles through ob_type aren't freed

Changes by Daniel Diniz : -- stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1441] Cycles through ob_type aren't freed

Changes by Christian Heimes: -- priority: -> normal type: -> behavior versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-

[issue1441] Cycles through ob_type aren't freed

New submission from Adam Olsen: If I create a subclass of 'type' that's also an instance of 'type', then I change __class__ to point to itself, at which point it cannot be freed (as the type object is needed to delete the instance.) I believe this can be solved by resetting __class__ to a known-