Message116379
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. |
|
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: <1284457751.09.0.666780694038.issue9815@psf.upfronthosting.co.za> |
2010-09-14 09:49:09 | pitrou | link | issue9815 messages |
2010-09-14 09:49:08 | pitrou | create | |
|