Georg Brandl <ge...@python.org> added the comment: This is caused by the fact that new-style classes create reference cycles. Try calling the cyclic garbage collector using gc.collect() after the function call, and the leaked references will vanish again.
---------- nosy: +georg.brandl resolution: -> duplicate status: open -> closed superseder: -> Declaring a class creates circular references _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9366> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
