[Python-Dev] cpython: #12586: add provisional email policy with new header parsing and folding.

R. David Murray rdmurray at bitdance.com
Sat May 26 15:37:28 CEST 2012


On Sat, 26 May 2012 09:14:07 +0200, Georg Brandl <g.brandl at gmx.net> wrote:
> Am 26.05.2012 00:44, schrieb r.david.murray:
> > http://hg.python.org/cpython/rev/0189b9d2d6bc
> > changeset:   77148:0189b9d2d6bc
> > user:        R David Murray <rdmurray at bitdance.com>
> > date:        Fri May 25 18:42:14 2012 -0400
> > summary:
> >   #12586: add provisional email policy with new header parsing and folding.
[...]
> > 
> > diff --git a/Doc/library/email.policy.rst b/Doc/library/email.policy.rst
> > --- a/Doc/library/email.policy.rst
> > +++ b/Doc/library/email.policy.rst
> > @@ -306,3 +306,326 @@
> >        ``7bit``, non-ascii binary data is CTE encoded using the ``unknown-8bit``
> >        charset.  Otherwise the original source header is used, with its existing
> >        line breaks and and any (RFC invalid) binary data it may contain.
[...]
> 
> There's a lot of new stuff here: should have a versionadded?  (Or do we need new
> markup for "provisional" stuff?)

The entire policy module is new in 3.3 and has a versionadded at the
top.

New markup for provisional would be cool, though.

I think eventually some of these docs will get factored out of policy,
but that probably won't happen until it is no longer provisional.
At that point I'll be doing a massive doc reorganization to deprecate
many of the old APIs.

Another option here is to consider 'policy' itself as the provisional
package...except that to use it requires hooks in the other packages
(the policy= keyword arguments).  And I'm pretty satisfied with the
API of the policy module itself, so I don't think it needs to be
considered provisional.

--David


More information about the Python-Dev mailing list