RetroSearch Browse

Sat Sep 12 17:13:46 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-September/141599.html

Someone else brought up warnings in Python 2.7 and my response was that you
already get the warning in Python 3 so why get it twice across different
versions?

On Fri, Sep 11, 2015, 22:48 Serhiy Storchaka <storchaka at gmail.com> wrote:

> On 08.09.15 19:59, Brett Cannon wrote:
> > The approaches to module deprecation I have seen are:
> > 1. Nothing changes to the deprecation process; you deprecate a module
> > and remove it in one to two releases
> > 2. Deprecate the module but with no plans for removal until Python 2.7
> > reaches its EOL (I have been calling this Python 4)
> > 3. Document the deprecation but no actual code deprecation
>
> Of course #2 LGTM. What if at the same time add Py3k warning in next 2.7
> bugfix release?
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150912/0e9cdc1d/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-September/141599.html below:

[Python-Dev] Choosing an official stance towards module deprecation in Python 3