map(print, list_of_tuples)
quite a bit, but that possibly an artifact of my print-based debugging. I can only do this with print as a function rather than a statement, and the single line makes it easy to drop in or comment out as needed.Not as nice, but doable.
Seeing how my transition to Py3 got hung up on sending bytes in and out of ZeroMQ sockets, I might stop that now.
Back to the for loop or join the strings as suggested below.
>>> from pprint import pprint; pprint(list_of_tuples)PRINT TO A FILE, OR STDERR print >> sys.stderr, "blah" What are those '>' signs here? Why two? What happens if I use one only?
Compare this to (py3k): print("blablah", file=sys.stderr)
PRINT WITHOUT NEW LINE sys.stdout.write('blah') I can't use print to print?
compare to: print("blah", end="")
DISABLE FLIUSH In python 2 there are 2 or 3 different ways to do that, all more complicated than each other. Compared to:
print("blah", flush=True)
Finally, it's a function, you can do everything you do with a function, use map, return a print from another function, include it in generator expressions etc...
You can. Compare the output from:
print "foo"
print "bar"
With that from: print "foo",
print "bar"