| |||||||||||||
Moving to Python 3Moving to Python 3Posted Feb 9, 2011 23:22 UTC (Wed) by euske (subscriber, #9300)In reply to: Moving to Python 3 by midg3t Parent article: Moving to Python 3
And just like IPv6, it will only add confusion to the users. I like many design choices made by Python3 people, but branding Python3 as the "next version" of Python2 was a big mistake. One should give it a different name when two languages are incompatible.
(Log in to post comments)
Moving to Python 3 Posted Feb 9, 2011 23:32 UTC (Wed) by bronson (subscriber, #4806) [Link]
Same only moreso for Perl6.
Moving to Python 3 Posted Feb 10, 2011 6:52 UTC (Thu) by flewellyn (subscriber, #5047) [Link]
>One should give it a different name when two languages are incompatible.
They did. It's called "Python3". The old one is called "Python2".
It's analogous in some ways to ALGOL 60 vs ALGOL 68. Same heritage, but different languages.
|
|||||||||||||