[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

Guido van Rossum added the comment: Yeah, I do not think anyone cares. :-) -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___

[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

Andre Roberge added the comment: Since all the messages I track so far (https://github.com/aroberge/friendly/blob/master/friendly/syntax_errors/message_analyzer.py) had been changed when going from 6.7 to 3.8, I had (incorrectly) assumed that all such error messages been changed to use

[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

Serhiy Storchaka added the comment: Not all "can't" in error messages were replaced by "cannot". $ find Parser Python Objects Modules -name '*.[ch]' | xargs egrep '".*[Cc]an'\''t.*"' | wc -l 181 $ find Parser Python Objects Modules -name '*.[ch]' | xargs egrep '".*[Cc]annot.*"' | wc -l 247

[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

Lysandros Nikolaou added the comment: We can change the wording to `cannot` in order for all of the error messages to be consistent. Would you like to propose a PR, Andre? -- ___ Python tracker

[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum, lys.nikolaou, pablogsal ___ Python tracker ___ ___ Python-bugs-list

[issue43748] Inconsistent grammar in new error message (introduced in 3.10.0a7)

New submission from Andre Roberge : Python version 3.10.0a7 added a more informative error message for: >>> f"{**k}" File "", line 1 (**k) ^ SyntaxError: f-string: can't use double starred expression here Previously, the message was simply "SyntaxError: invalid syntax". So, this