__del__(): Remove this because it prevents the garbage collector from

being able to free cycles containing MailList objects (see the gc
module's documentation under the gc.garbage attribute for details).

AFAICT, this has no effect on operations currently, because I believe
we are pretty rigorous about unlocking MailList objects explicitly.
This has a dramatic effect on memory leakage too, since there were/are
cycles containing these fairly heavyweight objects that previously,
the garbage collector couldn't free.

We'll need to watch carefully for stale locks being left around,
because I believe the MailList objects were at least being finalized
during process shutdown, but maybe not, and it's a very dubious
practice to be depending on anyway.

Note: this doesn't completely eliminate the unbounded memory growth,
although this in conjunction with shutting off the archiver appears to
improve the steady state of memory usage (and perhaps not
coincidentally greatly improves performance).

0 files changed, 0 insertions, 0 deletions