[Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release] (original) (raw)

Barry Warsaw barry at python.org
Fri Sep 17 03:53:17 CEST 2010

On Sep 16, 2010, at 09:34 PM, R. David Murray wrote:

Say we start with this bytes input:

To: Glyph Lefkowitz <glyph at twistedmatrix.com> From: "R. David Murray" <rdmurray at bitdance.com> Subject: =?utf-8?q?p=F6stal?= A simple message. Part of the responsibility of the email module is to provide that in text form on demand, so the application gets: To: Glyph Lefkowitz <glyph at twistedmatrix.com> From: "R. David Murray" <rdmurray at bitdance.com> Subject: pöstal A simple message. Now the application allows the user to do some manipulation of that, and we have: To: "R. David Murray" <rdmurray at bitdance.com> From: Glyph Lefkowitz <glyph at twistedmatrix.com> Subject: Re: pöstal A simple reply.

And of course, what happens if the original subject is in one charset and the prefix is in an incompatible one? Then you end up with a wire format of two RFC 2047 encoded words separated by whitespace. You have to keep those chunks separate all the way through to do that properly. (I know RDM knows this. :)

But I am open to being convinced otherwise. If everyone hates the BytesMessage/StringMessage API design, then that should certainly not be what we implement in email.

Just as a point of order, to the extent that we're discussing generic approaches to similar problems across multiple modules, it's okay that we're having this discussion on python-dev. But the email-sig has put in a lot of work on specific API and implementation designs for the email package, so any deviation really needs to be debated, discussed, and decided there.

-Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100916/9c60862a/attachment.pgp>

More information about the Python-Dev mailing list