On Feb 28, 2011, at 04:32 PM, R. David Murray wrote: >Well, fortunately I've been enjoying it, and the increased recognition >is certainly one of the rewards, so thank you.
Just wait 'til the hate mail starts. Fortunately, most of that's got raw 8-bit in the headers, so you're in luck. :) >Regardless, I think having some sort of introspection on the capabilities >of the Message object is a good idea, but let's hold off defining it >until later. I'd like the design to be informed by the requirements of >handling externally-defined Message classes, as well as those provided >by the email package itself. On the other hand, rather than getting >too complex, it may be sufficient/better to just define some sort of >"api version" that a class declares it provides. I suppose it could be >an ABC, though personally I don't really like ABCs (but I'm not sure why). I don't like them much either. Agreed that if YAGNI, there's no reason to add them, or introspection for capabilities. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Email-SIG mailing list Email-SIG@python.org Your options: http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
