A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Python 4: don't remove anything, don't break backward compatibility

[Python-Dev] Python 4: don't remove anything, don't break backward compatibilityOleg Broytman phd at phdru.name
Mon Mar 10 18:50:44 CET 2014
On Mon, Mar 10, 2014 at 04:37:45PM +0000, Brett Cannon <bcannon at gmail.com> wrote:
> On Mon Mar 10 2014 at 12:08:55 PM, Victor Stinner <victor.stinner at gmail.com>
> wrote:
> 
> > >> I suggest to wait less than 8 years
> > >> for Python 4.
> > >
> > > Why? What's special about 8 years?
> >
> > It's the time between Python 2.0 and 3.0.
> 
> But I'm willing to bet that's going to be an anomaly. Python 3 came into
> existence when it did so we didn't wait too long for Python 2 to get even
> more of a foothold; the expectation is that long-term more non-Python 2
> code will be written than not. There's no rush on Python 4 since there are
> no plans to try and tweak something as drastic as str/bytes.

   Well, the entire discussion is about "please don't do major changes
-- we've got enough already".

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.
More information about the Python-Dev mailing list

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