<div><div dir="ltr"><div>Nick Coghlan made a pretty elaborated blog post about that here:Â <a href="http://opensource.com/life/14/9/why-python-4-wont-be-python-3" style="font-size:12pt" target="_blank">http://opensource.com/life/14/9/why-python-4-wont-be-python-3</a></div> </div></div></blockquote><div><br></div><div>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 :-).<br></div></div><br>-- <br><div class="gmail_signature">--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div>
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