4 ms·

This ship sailed 10 years ago. It's too little too late. The real question is whether python3 can avoid the same fate...

• sigzero 11y ago
  Python 3 is not even in the same boat. Please stop trolling.
  • deleted 11y ago
    [deleted]
• baldfat 11y ago
  I would say that they are different issues. Python 3 really is almost 7 years old and it is moving forward. The Wall of Shame has become the Wall of Super Powers. The scope for Python 3 was different than Perl 6. Perl 6 was to be ageless and for all time. Python 3 was a fix to a broken issues in Python 2 having redundant ways to do things. > Python 3.0 was developed with the same philosophy as in prior versions. However, as Python had accumulated new and redundant ways to program the same task, Python 3.0 had an emphasis on removing duplicative constructs and modules, in keeping with "There should be one— and preferably only one —obvious way to do it". https://en.wikipedia.org/wiki/History_of_Python https://en.wikipedia.org/wiki/History_of_Python I don't mind there being more than one way to do things.
• zoffix222 11y ago
  A completely different issue. Python3 is an upgrade to Python2. Perl 6 became a new language, while Perl 5 still chugging along at full speed (latest stable release was just 4 months ago).