Jan. 1, 2002
2:21 p.m.
"TFH" == Tollef Fog Heen <tollef@add.no> writes:
TFH> * (Barry A. Warsaw)
BAW> One thing though: while I /think/ the membership api is
BAW> nicely separated and can be easily replaced, other list
BAW> configuration variables are not. So you'll still see lots of
BAW> direct attribute access on MailList objects. Meaning it's
BAW> much tougher to divert non-membership data to an external
BAW> source.
TFH> Why is that, if you replace the normal MailList objects with
TFH> some opaque objects using __getattr__ and __setattr__ for
TFH> getting the data out of somewhere else?MM2.1 already uses __getattr__() as a hamfisted way of implementing the gui (web) components, so overriding these in a MailList derived class would be a little tricky.
Python 2.2 provides some hope here, with its descriptors and properties, and this is one of the things I'd like to explore for MM-the-next-generation-after-2.1.
Cheers, -Barry