2 ms·
> Python broke backwards compatibility for as simple a thing like a print statement. Nobody like to play stupid expensive migration games just because your lang
by zokier 14y ago
> Python broke backwards compatibility for as simple a thing like a print statement. Nobody like to play stupid expensive migration games just because your language designer decided that print statement must be written a different way.
That is a silly argument. They didn't break compatibility because they wanted to change the way print is. They changed the print because they already had decided to break compatibility. Ie "lets break compatibility to change print" vs "while we are breaking stuff, lets fix the print too"
- saurik 14y agoThe idea of "breaking compatibility" is not really a boolean: it is measured in the scalar unit of "difficulty required to regain compatibility".
- zokier 14y agoIn that case I'd say changing print would belong to the "trivial" end of the scale. Print function was backported to Python 2.6, so you can easily write code that is compatible with both. And modifying existing code is so trivial that even an automated tool (2to3) can do it reliably.