[Mailman-Developers] Patch: Optionally Suppressing List Headers

[Jay R. Ashworth]

On Thu, Apr 05, 2001 at 09:55:54AM -0400, Barry A. Warsaw wrote:
>     JRA> Because then, at least old unchanged objects which were read
>     JRA> in by the 'code inside the object' wouldn't break: they'd
>     JRA> just have to pick up the default for that attribute.  When
>     JRA> you wrote them *back out*, they'd automagically be fixed.
> 
> This happens now, since once that attribute's on the MailList object,
> it'll get written back out to the .db file.

Oh.  It sounded to *me* like the read-in would fail.  Misunderstood.

Then what's the problem?

>     JRA> Are pickles less prone to break the "objectization" of
>     JRA> objects you're going to want persistent storage of?
> 
> I'm not sure I understand the question.  Marshal only handles built-in
> types (ints, longs, dicts, lists, tuples) and wasn't designed to
> handle instances.  That's what pickle is for (and see the cPickle
> module for a really fast implementation of the pickle protocol).

Um, "nevermind".

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra@baylink.com
Member of the Technical Staff     Baylink
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 804 5015