News for hackers. Stuff that matters.

A comment on The Linux 2.5, Ruby 1.9 and Python 3 release management anti-pattern. Parent comment

Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a... by rspeer on Tuesday December 27, 2016 @04:23AM (#13262173)
As much as I want Python 3 to replace Python 2, you can't recommend 2to3 while saying "Enough with the bullshit". 2to3 is abandonware that never worked.

Now you can use python-future instead, a third-party solution, but the 2to3 part of the PEP was a false promise that gave ammo to Python 2 fans.

[ Parent | on HN ]
Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a... by zodiac on Tuesday December 27, 2016 @05:30AM (#13262384)
> the 2to3 part of the PEP was a false promise that gave ammo to Python 2 fans

The PEP (3105) doesn't actually mention 2to3 anywhere, it just says that the fact that print is a statement (ie handled explicitly in the language syntax) means it is easy to write a tool to do the conversion automatically. Which is a perfectly valid point, even if 2to3 fails to do that for some reason.

[ Parent | on HN ]