News for hackers. Stuff that matters.

A comment on Moving Away from Python 2. Parent comment

Re:Moving Away from Python 2 by daveguy on Friday May 20, 2016 @07:56PM (#11742454)
It is pretty obvious there is a problem when your quick and easy cheat sheet is a 33 page tomb. If only Guido and company would acknowledge the problem and fix it instead of putting their fingers in their ears pretending Python 2 will cease to exist in 2020.
[ Parent | on HN ]
Re:Moving Away from Python 2 by wnoise on Friday May 20, 2016 @09:35PM (#11742740)
They acknowledge the problem, and their solution is to stop actively aiding and abetting the people who are continuing to make it worse by writing python 2 code.
[ Parent | on HN ]
Re:Moving Away from Python 2 by nomel on Friday May 20, 2016 @11:12PM (#11743012)
Wow, what a simplification.

What about us who have and want to use massive libraries of existing Python 2 code?

"Just upgrade your libraries!" is not realistic for everyone, especially those who have to justify a mostly idealogical conversion to a similar language, and spend real time and money, outside of actually developing the end product, to do it.

Four more years of official support is a long time.

[ Parent | on HN ]
Re:Moving Away from Python 2 by takeda on Saturday May 21, 2016 @01:49AM (#11743384)
Someone suggested Cython to compile python 2 code as modules and import to python 3. Did not try it, but that sounds plausible.
[ Parent | on HN ]