[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Brett Cannon bcannon at gmail.com
Mon Mar 10 17:37:45 CET 2014
- 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 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140310/37ab2019/attachment.html>
- 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 ]