Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
Closed
Description
Bug report
Bug description:
This report was originally launchedhere.
grammars:
3.12.0rc3
3.13.0 alpha 0
Rule name conflict with the follwing two grammar rules:
fstring: star_expressions
and
fstring: | FSTRING_START fstring_middle* FSTRING_END
The colon sign is not a soft keyword (":"), it is a token (':') in these rules:
type_param: | NAME [type_param_bound] | '*' NAME ":" expression | '*' NAME | '**' NAME ":" expression | '**' NAMEtype_param_bound: ":" expression
The equal sign is not a soft keyword ("="), it is a token ('=') in the following rule:
fstring_replacement_field: | '{' (yield_expr | star_expressions) "="? [fstring_conversion] [fstring_full_format_spec] '}'
These are more just notation problems in the previous two cases.
In general, this is a problem from that point of view that comparing two texts is slower than comparing two integers.
CPython versions tested on:
3.12
Operating systems tested on:
No response