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

Showing content from http://mail.python.org/pipermail/python-dev/2014-March/133067.html below:

don't remove anything, don't break backward compatibility

• Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 3/10/2014 12:29 PM, Chris Angelico wrote:

> I don't think there'd be huge problems
> with a 4.0 release that's just like 3.10 except that it's a little
> more free with removal of deprecateds. Maybe that could be the point
> at which 2.x compatibility is dropped,

... and the point at which those of us on 2.x jump over 3.x to 4.x.  :)

Emile

• Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• 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