[Mailman-Developers] Re: [Mailman-Users] [RELEASED] Mailman 2.1 alpha 3

[Tollef Fog Heen]

*  (Barry A. Warsaw)

| One thing though: while I /think/ the membership api is nicely
| separated and can be easily replaced, other list configuration
| variables are not.  So you'll still see lots of direct attribute
| access on MailList objects.  Meaning it's much tougher to divert
| non-membership data to an external source.

Why is that, if you replace the normal MailList objects with some
opaque objects using __getattr__ and __setattr__ for getting the data
out of somewhere else?

-- 

Tollef Fog Heen
Axiom #1: You Can't Win