Re:No-op statements syntactically valid only since Python X.Y
by eesmith on Monday June 06, 2022 @11:40AM
(#31641878)
I think "six" proved more useful than 2to3. This made it easier to support both Python 2 and Python 3 in the same code base, which (IMO) resulted in a smoother migration path.
[ Parent
| on HN ]
Re:No-op statements syntactically valid only since Python X.Y
by xenophonf on Monday June 06, 2022 @11:59AM
(#31642150)
You're absolutely right, and again, I think that reinforces how important a good migration path was to Python 3. Without that path, I think there was a real risk of Python dying off same as Perl 5.
It's sad because there was a lot I liked about Perl. I wish that community had better leadership because from my quick glance at the Wikipedia page, it looks like the Perl 7 project is making the same mistakes as Perl 6/Raku did. It's really too bad.