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 vstinner
Recipients Demur Rumed, Mark.Shannon, serhiy.storchaka, vstinner, yselivanov
Date 2016-09-09.05:47:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Known issues:
> * test_traceback and test_extcall fail
> * _PyEval_EvalCodeWithName2() should be merged into _PyEval_EvalCodeWithName() to factorize the code

I fixed test_extcall and removed _PyEval_EvalCodeWithName2(): callfunc-8.patch.

I don't know how to fix test_traceback.

@Serhiy: I really need the patch tomorrow. Would you mind to push it? If you are unable to fix test_traceback, just skip the test with a FIXME and open a new issue (it should be easy to fix it later).

I really want to finish METH_FASTCALL, issue #27810, before the first beta next monday and basically tomorrow is for me the last time when I can still push things.

If we really find a major design issue, you still have 3 to 4 months to revert the change. If we find a minor design flaw or another optimization, again, we will still have time to enhance the code during the beta stage. The most important part is to push the major change to reduce changes after the first beta.
Date User Action Args
2016-09-09 05:47:44vstinnersetrecipients: + vstinner, Mark.Shannon, serhiy.storchaka, yselivanov, Demur Rumed
2016-09-09 05:47:39vstinnersetmessageid: <>
2016-09-09 05:47:39vstinnerlinkissue27213 messages
2016-09-09 05:47:39vstinnercreate