On Mon, Dec 15, 2014 at 4:38 PM, Michael Torrie <torr...@gmail.com> wrote: > Thought I had indirectly, since I've been using this print technique for > the last few days. Good to know it works either way, though. Guess the > future import is only to make not having parens and error.
Yeah. I usually recommend using parens and a single native-string argument, for maximum portability. That'll work even on pre-2.6 where the future import isn't supported. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
