[Python-Dev] Handling deprecations in the face of PEP 384

Brett Cannon brett at python.org
Sun Apr 22 00:13:57 CEST 2012


On Sat, Apr 21, 2012 at 16:55, "Martin v. Löwis" <martin at v.loewis.de> wrote:

> > From my reading of PEP 384 that means I would need to at least deprecate
> > PyImport_getMagicTag(), correct (assuming I follow through with this; I
> > might not bother)?
>
> All that PEP 384 gives you is that you MAY deprecate certain API
> (namely, all API not guaranteed as stable). If an API is not in the
> restricted set, this doesn't mean that it SHOULD be deprecated at
> some point. So there is no need to deprecate anything.
>

I meant "at least deprecate" as in "I can't just remove it from Python 3.3".

-Brett


>
> OTOH, if the new implementation cannot readily support the
> API anymore, it can certainly go away. If it was truly private
> (i.e. _Py_*), it can go away immediately. Otherwise, it should be
> deprecated-then-removed.
>
> Regards,
> Martin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120421/f8cad7d0/attachment.html>


More information about the Python-Dev mailing list