Raymond Hettinger <python <at> rcn.com> writes: > > P.S. My other experience with 3.0 is that my most frequent error has > changed. It used to be that the number reason for my getting a syntax > error was leaving-off a colon. Now, my number one reason is > omitting parens in a print() function call. I thought I would get used to > it quickly, but it still comes up several times a day.
I find myself with the reverse problem. When I code with 2.x, I often put parens around the argument list of a print staement. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
