[Email-SIG] Converting to quoted printable encoding
barry at python.org
Fri Sep 26 22:53:57 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Sep 25, 2008, at 4:30 PM, Mark Sapiro wrote:
> I suppose the ideal solution to all of this is that the encoder should
> first look at the existing Content-Transfer_Encoding header if any to
> see if the payload is already encoded, and if no header, encode and
> add the header; if existing header with target encoding, do nothing,
> and if existing header with other encoding, decode, encode and replace
> the header. However it doesn't work that way.
I think there are lots of opportunities for cleaning up the email
package API. I still believe there are fundamental semantic problems
in the 3.0 version of the package, mostly due to the bytes/unicode
split. I really wish I had had time to complete that work, but alas
we never got around to it at Pycon.
I'd like to jump start the discussion on a next version of the email
package, one that plays better with Python 3.0 (but would still be
Python 2.6 and possibly 2.5 compatible).
We should probably begin by enumerating all the things we think are
wrong with the current email package. Perhaps we could use the wiki
on python.org for that. Thoughts?
If you agree, I'll try to set some things up over there.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
-----END PGP SIGNATURE-----
More information about the Email-SIG