Python 3 in 2016

Re:Python 3 in 2016 by sametmax on Thursday February 18, 2016 @08:11AM (#11125450)

Python 3 is much more than changing the print() statement (which, actually, is a great thing). It's about unicode by default. It's about removing 100 of duplicates way to do things to have only one. It's about making debug much, much easier, while at the same time allowing you to write better code with less mistakes. It's about removing a lot of boilerplate. It's about introducing new syntaxes allowing things not possible in python 2.

If you see only print, you are missing the point.

But good news, there are many projects working to improve the perfs and/or bypass the GIL this year.

[ Parent | on HN ]

Re:Python 3 in 2016 by plesner on Thursday February 18, 2016 @10:03AM (#11126190)

> If you see only print, you are missing the point.

The top thing, sometimes the only thing, that makes my scripts written for 2 not work in 3 is the change to print. Adding a print function is fine, I'm all on board with that; removing the statement though seems like pain for no reason. Bringing that up is not missing the point, it's hitting the nail right on the head.

[ Parent | on HN ]

Re:Python 3 in 2016 by JupiterMoon on Thursday February 18, 2016 @12:25PM (#11127477)

I think you might want to look into the 2to3 script. It should handle the conversion of your print statements.

[ Parent | on HN ]