On Tue, Jan 14, 2020, at 18:15, David Mertz wrote: > For what it's worth, after 20+ years of using Python, forgetting the > colon for blocks remains the most common error I make by a fairly wide > margin. Of course, once I see the error message—even being not all that > descriptive of the real issue—I immediately know what to fix too.
What if the colon were made optional, with an eye to perhaps eventually no longer using it as the preferred style for new code? We had a post a while ago about the possibility of using the lack of a colon as an implicit line continuation (like with parentheses, e.g. "if a\nand b:", and this was (reasonably) rejected. But if a line beginning as a compound statement and ending without a colon is *never* going to have a valid meaning as something else... what's the point of the colon, otherwise? Seems like just grit on the screen. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/J47TEY2KFGATFMQ7RSZJO7B4RV7KEYWJ/ Code of Conduct: http://python.org/psf/codeofconduct/
