Message 116379 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	eric.araujo, ocean-city, pitrou
Date	2010-09-14.09:49:08
SpamBayes Score	1.0554645e-08
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2010-09-14 09:49:11	pitrou	set	recipients: + pitrou, ocean-city, eric.araujo
2010-09-14 09:49:11	pitrou	set	messageid: <[email protected]>
2010-09-14 09:49:09	pitrou	link	issue9815 messages
2010-09-14 09:49:08	pitrou	create