R. David Murray added the comment:
The new email API (which was just made non-provisional) uses a "sniff"
technique to decide what CTE to use for text bodies set via set_content. So I
consider this done (finally). It does not change MIMEText, which is now the
legacy API.
--
Dmitry Shachnev mity...@gmail.com added the comment:
This seems to be an enhancement sort of request rather than a bug... so I
wonder why Python 3.2 is listed?
Fixed.
... although I see nothing in the PEP about how to access that information
from Python.
You are right, it seems there is
R. David Murray rdmur...@bitdance.com added the comment:
Well, the original change to using utf-8 by default was considered a bug fix.
But I suppose you are right that this goes beyond that into enhancement
territory. In which case we could wait for an enhancement to the C API to base
it
Glenn Linderman v+pyt...@g.nevcal.com added the comment:
Patch is interesting, using an encoder to detect validity. However, it suffers
from some performance problems for long text that has large ASCII prefixes.
This seems to be an enhancement sort of request rather than a bug... so I
wonder
R. David Murray rdmur...@bitdance.com added the comment:
Thanks for the patch. I may not get to this until after the beta (or I might,
you never know).
Could you submit a contributor agreement please?
http://www.python.org/psf/contrib
--
stage: - patch review
title: [patch] add
Dmitry Shachnev mity...@gmail.com added the comment:
Done, sent an e-mail to contribut...@python.org.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15016
___
