3 ms·

I still don't get why they are noy just backporting the simple things people are missing. Like breaking: print "hello". I don't think being academically correct

• kstrauser 10y ago
  That's far and away the easiest transition: start using parens in your Python 2.7 code today and you won't have to alter them when migration day comes.
  • iak8god 10y ago
    And use __future__ to force yourself not to forget: https://docs.python.org/2/library/__future__.html https://docs.python.org/2/library/__future__.html
• ta_389ty4 10y ago
  You can fix this with one bash command, or an IDE, or whatever. Sounds like the people who can't upgrade are just , well, you fill in the word yourself.
• Karunamon 10y ago
  Call me strange but I actually like that change. Not because I enjoy typing more, but because invalid syntax errors on print is an unambiguous warning that whatever code I just downloaded and ran is incompatible with 2.x Without that, there may be other much more subtle bugs I'd have missed and spent time troubleshooting.
• pmorici 10y ago
  Python 3 ships with a utility that fixes that stuff with no work on your part just run 2to3 on all you're Python 2 source and like 99% of the differences are taken care of.
  • nomel 10y ago
    Why not have "print thing" to "print(thing)" just be an automatic conversion though?
    • pmorici 10y ago
      It's is, that is what the 2to3 program does automatically converts that among other things.