➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients aeros, eric.smith, gvanrossum, lys.nikolaou, pablogsal, petr.viktorin, serhiy.storchaka, vstinner
Date 2020-04-29.19:18:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLfwXKxXhpK2EFie5o_O_FpphKJB6_tRSxPiK0+=Fv73w@mail.gmail.com>
In-reply-to <1588187507.46.0.608923763039.issue40246@roundup.psfhosted.org>
Content 
If it's all handled by the tokenizer, how come it's different in the new
parser?

Anyway, it seems we really have to support what the old parser supported
here. I don't know exactly what rules it uses. Maybe only look for a string
quote following a name that can definitely be a string prefix?
History
Date User Action Args
2020-04-29 19:18:31gvanrossumsetrecipients: + gvanrossum, vstinner, eric.smith, petr.viktorin, serhiy.storchaka, lys.nikolaou, pablogsal, aeros
2020-04-29 19:18:31gvanrossumlinkissue40246 messages
2020-04-29 19:18:31gvanrossumcreate