Antoine Pitrou <pit...@free.fr> added the comment: You shouldn't use DEBUG_LEAK except for debugging purposes :)
As the doc mentions: “To debug a leaking program call gc.set_debug(gc.DEBUG_LEAK). Notice that this includes gc.DEBUG_SAVEALL, causing garbage-collected objects to be saved in gc.garbage for inspection.” It's true that the message at shutdown should be eliminated in this case, though. Anyway, I've committed a fix in r84798. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9815> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
