On Wed, Dec 2, 2015 at 7:32 AM, Emanuel Barry <vgr255 at live.ca> wrote: > Nick Coghlan made a pretty elaborated blog post about that here: > http://opensource.com/life/14/9/why-python-4-wont-be-python-3 > I wholeheartedly agree with what Nick writes there -- but I can't resist noting that the title is backwards -- the whole point is that Python 4 *will* be like Python 3, i.e. it will *not* differ (in a backward-incompatible way) from Python 3. What Nick probably meant is "Why the *transition to* Python 4 won't be like the transition to Python 3." And that is exactly right. We've learned our lesson (though we're in much better shape than Perl :-). -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20151202/cf801026/attachment.html>
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