From f20ac2ed076df63a77f65ff2660148af9f1a9b3c Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Tue, 22 Feb 2022 02:00:50 -0800 Subject: bpo-46820: Fix a SyntaxError in a numeric literal followed by "not in" (GH-31479) (GH-31493) Fix parsing a numeric literal immediately (without spaces) followed by "not in" keywords, like in "1not in x". Now the parser only emits a warning, not a syntax error. (cherry picked from commit 090e5c4b946b28f50fce445916c5d3ec45c8f45f) Co-authored-by: Serhiy Storchaka --- Parser/tokenizer.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'Parser/tokenizer.c') diff --git a/Parser/tokenizer.c b/Parser/tokenizer.c index eb15ef7a5d5..267ccec33fd 100644 --- a/Parser/tokenizer.c +++ b/Parser/tokenizer.c @@ -1251,6 +1251,9 @@ verify_end_of_number(struct tok_state *tok, int c, const char *kind) else if (c == 'o') { r = lookahead(tok, "r"); } + else if (c == 'n') { + r = lookahead(tok, "ot"); + } if (r) { tok_backup(tok, c); if (parser_warn(tok, "invalid %s literal", kind)) { -- cgit v1.2.3-65-gdbad