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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4