René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unhelpful `SyntaxError` with unclosed call before colon","articleBody":"Ran into this today. If you forget to close parentheses as part of a call in the header of a `for`, `with`, or `class` statement (maybe others too?), the `SyntaxError` seems to indicate that you forgot a colon:\r\n\r\n```py\r\n\u003e\u003e\u003e for foo in bar(baz:\r\n  File \"\u003cstdin\u003e\", line 1\r\n    for foo in bar(baz:\r\n                  ^\r\nSyntaxError: expected ':'\r\n```\r\n\r\nIt's not *wrong*, but could probably be improved. I personally find the pre-3.10 behavior more helpful:\r\n\r\n```py\r\n\u003e\u003e\u003e bar(baz:\r\n  File \"\u003cstdin\u003e\", line 1\r\n    for foo in bar(baz:\r\n                      ^\r\nSyntaxError: invalid syntax\r\n```\r\n\r\nEven better, though, would be a \"smarter\" error message like the existing ones we have for unclosed parentheses:\r\n\r\n```py\r\n\u003e\u003e\u003e bar(baz:\r\n  File \"\u003cstdin\u003e\", line 1\r\n    for foo in bar(baz:\r\n                  ^\r\nSyntaxError: '(' was never closed\r\n```\r\n\r\n@pablogsal","author":{"url":"https://github.com/brandtbucher","@type":"Person","name":"brandtbucher"},"datePublished":"2022-06-20T17:32:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/94034/cpython/issues/94034"}