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 pablogsal
Recipients aroberge, hsfzxjy, pablogsal, terry.reedy
Date 2021-02-08.20:59:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1612817992.01.0.370136405133.issue43163@roundup.psfhosted.org>
In-reply-to
Content
> (I think it would be good if a C expert compared it to the *current* C code.)

That would be very beneficial but is quite a big task, specially given that codeop design is quite surprising. I personally find quite confusing the way codeop is handling the decisions on continuing or not (is based on compiling the code with different levels of new lines and then checking the repr() of the exceptions). It would be good if someone familiar with "codeop" design can take a look on what's the best way to proceed.
History
Date User Action Args
2021-02-08 20:59:52pablogsalsetrecipients: + pablogsal, terry.reedy, aroberge, hsfzxjy
2021-02-08 20:59:52pablogsalsetmessageid: <1612817992.01.0.370136405133.issue43163@roundup.psfhosted.org>
2021-02-08 20:59:52pablogsallinkissue43163 messages
2021-02-08 20:59:51pablogsalcreate