GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Unhelpful `SyntaxError` with unclosed call before colon · Issue #94034 · python/cpython Closed as not planned Labels 3.10 (EOL)end of lifeend of life3.11only security fixesonly security fixes3.12only security fixesonly security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)type-featureA feature request or enhancementA feature request or enhancement DescriptionRan into this today. If you forget to close parentheses as part of a call in the header of a >>> for foo in bar(baz: File "<stdin>", line 1 for foo in bar(baz: ^ SyntaxError: expected ':' It's not wrong, but could probably be improved. I personally find the pre-3.10 behavior more helpful: >>> bar(baz: File "<stdin>", line 1 for foo in bar(baz: ^ SyntaxError: invalid syntax Even better, though, would be a "smarter" error message like the existing ones we have for unclosed parentheses: >>> bar(baz: File "<stdin>", line 1 for foo in bar(baz: ^ SyntaxError: '(' was never closed Activity
MetadataMetadataAssigneesLabels3.10 (EOL)end of lifeend of life3.11only security fixesonly security fixes3.12only security fixesonly security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)type-featureA feature request or enhancementA feature request or enhancement ProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |