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 xxm
Recipients gvanrossum, lys.nikolaou, serhiy.storchaka, terry.reedy, xxm
Date 2021-01-16.03:31:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1610767865.83.0.94994957984.issue42889@roundup.psfhosted.org>
In-reply-to
Content
Thank you for your kindly explanations! The output of the first program in msg384799 behaves as expected from the view of AST compiling.  Yes,I see now. But for the second example in msg384879, the behaviors are inconsistent between old Python version(3.6,3.7,3.8) and new Python version(3.9,3.10). It is probably something wrong in "compile" parsing bool string, "False","True" in new version of Python(3.9,3.10). 

I think a checker in function "compile" will not be complicated. Like you said, the simplest way I can think is to re-perform lexical analysis and syntax analysis. e.g. unparse ast, then parse ast before compiling AST object. 

As for #42887, only part of attributes will lead to that bug. I think it's attribute-related. If that bug is triggered by c loop, all attributes should be involved.
History
Date User Action Args
2021-01-16 03:31:05xxmsetrecipients: + xxm, gvanrossum, terry.reedy, serhiy.storchaka, lys.nikolaou
2021-01-16 03:31:05xxmsetmessageid: <1610767865.83.0.94994957984.issue42889@roundup.psfhosted.org>
2021-01-16 03:31:05xxmlinkissue42889 messages
2021-01-16 03:31:05xxmcreate