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

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

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

• Previous message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
• Next message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mar 17, 2011, at 4:07 PM, Raymond Hettinger wrote:
> Agreeing with Guido is always a good move :-)
> 
> In addition, any new deprecations in Py3.x can be marked with py3k warnings in Py2.7 point releases.  That would give users the maximum chance to make updates before porting, even if they wait five years to migrate to Py3.x.

And of course, updating 2to3, if possible, would also be appreciated.

James

• Previous message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
• Next message: [Python-Dev] API deprecations in Python 3, from a Python 2 perspective
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4