RetroSearch Browse

Fri Mar 18 00:46:48 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109464.html

On Thu, Mar 17, 2011 at 8:35 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Thu, 17 Mar 2011 19:23:30 -0400
> Terry Reedy <tjreedy at udel.edu> wrote:
>> People should retest their stuff with
>> each micro (bugfix) release anyway.
>
> I'm not sure they should. The point of having micro releases is that
> they don't bring any visible change in behaviour - apart from fixing
> bugs, that is.

But IMHO, it would be that, or urging people to use 2to3 from a separate source.
It does not make sense to keep 2to3 frozen while its target moves
forward. Even if
it is decided that things should not be removed, 2to3 should warn of new
deprecations as Python moves into 3.3, 3.4, and beyond.

    js
  -><-
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/jsbueno%40python.org.br
>

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109464.html below:

[Python-Dev] API deprecations in Python 3, from a Python 2 perspective