cpython/Parser/pegen
Lysandros Nikolaou ae14583302
bpo-40334: Produce better error messages for non-parenthesized genexps (GH-20153)
The error message, generated for a non-parenthesized generator expression
in function calls, was still the generic `invalid syntax`, when the generator expression wasn't appearing as the first argument in the call. With this patch, even on input like `f(a, b, c for c in d, e)`, the correct error message gets produced.
2020-05-22 01:56:52 +01:00
..
parse.c bpo-40334: Produce better error messages for non-parenthesized genexps (GH-20153) 2020-05-22 01:56:52 +01:00
parse_string.c bpo-40334: Fix error location upon parsing an invalid string literal (GH-19962) 2020-05-07 11:37:51 +01:00
parse_string.h bpo-40334: Fix error location upon parsing an invalid string literal (GH-19962) 2020-05-07 11:37:51 +01:00
peg_api.c bpo-40334: Make the PyPegen* and PyParser* APIs more consistent (GH-19839) 2020-05-01 18:30:51 +01:00
pegen.c bpo-40334: Produce better error messages for non-parenthesized genexps (GH-20153) 2020-05-22 01:56:52 +01:00
pegen.h bpo-40334: Produce better error messages for non-parenthesized genexps (GH-20153) 2020-05-22 01:56:52 +01:00