Greetings,
I'm new to Mailman development, so bear with me. I didn't see
anything in the archives addressing this, but my searches weren't
too complex.
There's probably good reason for this design, but why have
multiple dicts within the MailList infrastructure duplicating
the subscriber list?
In [config.pck]:
'passwords': { '[EMAIL PROTECTED]': 'pass',
'[EMAIL PROTECTED]': 'pass' }
'members': { '[EMAIL PROTECTED]': 0,
'[EMAIL PROTECTED]': 0 }
'usernames': { '[EMAIL PROTECTED]': u'Subscriber One!',
'[EMAIL PROTECTED]': u'Subscriber Two!' }
'user_options: { '[EMAIL PROTECTED]': 264,
'[EMAIL PROTECTED]': 392 }
Seems like it would be more straightforward (in design, at
least; maybe not in practice) to store it with nested dicts like:
'subscribers': { '[EMAIL PROTECTED]': { 'password': 'pass',
'digest': 0,
'username': u'Subscriber One!',
'options': 264 }
'[EMAIL PROTECTED]': { 'password': 'pass',
'digest': 1,
'username': u'Subscriber Two!',
'options': 392 }
}
There tends to be more consistency with this approach than, for
instance, having a members dict *and* a digest_members dict
which could each be empty. Why not just toggle a subvalue
within a master subscriber database dict?
Thanks,
-Drew
_______________________________________________
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
