In a dict literal, using a variable that contains a keyword (such as in, yield, for, ...) as a substring in a variable name confuses the syntax highlighter, causing it to mark the comma as an error.
For example:

# For copy/pasting:
{
"a": something,
"b": form, # includes `for`
"c": defend, # includes `def`
"d": fine, # includes `in`
"e": asynchronous, # inclues `async`
}
Using build 3200 on linux.
This is #1896, right? Edit: Whoops! I think that's a "yes, but with lots more reserved words"
@michaelblyons Yes, that appears to be the same issue.
To be fixed by #1896. Only the line with "for" causes this behavior, as removing that causes the invalid scopes on the commas to disappear.

This issue has been solved by a previous commit, hence it is being closed.
Most helpful comment
To be fixed by #1896. Only the line with "for" causes this behavior, as removing that causes the invalid scopes on the commas to disappear.