[Mailman-Developers] The one-giant-object approach

[emf]

Gentlebeings,

I'm trying to hook up the object-relational mapper I've worked out to
mailman, and I'm encountering an issue I'd appreciate feedback on.

Take MailList. Aside from its own namespace, it mixes in 11 other
classes, leading to 255 names if you dir(list).

Is this large, flat namespace a preference? It seems to me like it mixes
together many bits of functionality that aren't always needed by
whatever code needs a 'list'.

It seems to me that if things were broken up a little bit they'd be
conceptually easier to follow, and it'd be easier to make improvements.

While I understand that a unified DB likely won't make it into 2.2, I 
would like to break out some functionality, and I just wanted to make 
sure that keeping a flat namespace wasn't a design goal.

Thanks,

~ethan fremen