News for hackers. Stuff that matters.
Re:Code that will break in Python 4 by andrewingram on Tuesday January 12, 2016 @11:36AM (#10888374)
Is there a reason why any future syntax changes cannot be handled using transpilers in the same way it's worked for the JavaScript community? Such transpilers do exist for Python, but they never really saw much use, is it because 3to2 came along too late, and for a long time we only had the option of 2to3?

ie once future syntax develops, start using it immediately using a transpiler, and have builds that target as many versions as you care to support.

Re:Code that will break in Python 4 by knughit on Tuesday January 12, 2016 @11:46AM (#10888432)
Because Python's philosophy is that the language designers known the one best way to do everything.
Re:Code that will break in Python 4 by s73v3r on Tuesday January 12, 2016 @12:40PM (#10888876)
Because it's not just syntax changes.
Re:Code that will break in Python 4 by andrewingram on Tuesday January 12, 2016 @01:09PM (#10889123)
Same with Babel in JavaScript-land, there's a runtime module for changes that can't be achieved with a syntax transform alone.