In Python 3.10.1, a change occurred compared with 3.10.0 so that an incorrect token is flagged for a SyntaxError.  Also, in 3.11.0a2, the suggestion made about having forgotten a comma is incorrect.


Python 3.10.1
    for x range(4):
                  ^
SyntaxError: invalid syntax

(I no longer have 3.10.0 available but I know from my tests that it was identifying correctly the wrong token.)


Python 3.11.0a2
    for x range(4):
        ^^^^^^^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

Python 3.9.5
    for x range(4):
          ^
SyntaxError: invalid syntax

Python 3.8.10
    for x range(4):
          ^
SyntaxError: invalid syntax

Python 3.7.8
    for x range(4):
              ^
SyntaxError: invalid syntax

Python 3.6.8
    for x range(4):
              ^
SyntaxError: invalid syntax

From (https://friendly-traceback.github.io/docs/syntax_tracebacks_en_3.10.html#for-loop-missing-in-operator), this is what was shown for Python 3.10.0

    for x range(4):
        ^^^^^^^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

Same as Python 3.11.0a2.

New changeset 1c7a1c3be08ee911d347fffd2716f3911ba751f9 by Pablo Galindo Salgado in branch 'main':
bpo-46004: Fix error location for loops with invalid targets (GH-29959)
https://github.com/python/cpython/commit/1c7a1c3be08ee911d347fffd2716f3911ba751f9

New changeset c52141200364898818956a73b955f7c04f634dc8 by Pablo Galindo Salgado in branch '3.10':
[3.10] bpo-46004: Fix error location for loops with invalid targets (GH-29959). (GH-29961)
https://github.com/python/cpython/commit/c52141200364898818956a73b955f7c04f634dc8

>    From (https://friendly-traceback.github.io/docs/syntax_tracebacks_en_3.10.html#for-loop-missing-in-operator), this is what was shown for Python 3.10.0

Yeah, we are not showing that anymore as we only trigger the error when it happens inside collections to avoid many of the false positives we were seeing.

This PR fixes the problem to point to the correct token, but still show "syntax error"