➜

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 methane, serhiy.storchaka, vstinner
Date 2017-02-08.15:39:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486568378.9.0.904847418882.issue29502@psf.upfronthosting.co.za>
In-reply-to
Content 
call_function() and do_call_core() functions of Python/ceval.c use C_TRACE() macro to call the profiler, but PyObject_Call() and similar functions like _PyObject_FastCallKeywords() don't.

Is it a bug or a deliberate choice for performance?

Since PyObject_Call() and similar functions have now fast paths, I don't think that it's still needed to have these fast paths in ceval.c too. But I kept fast paths in ceval.c because of C_TRACE().
History
Date User Action Args
2017-02-08 15:39:38vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2017-02-08 15:39:38vstinnersetmessageid: <1486568378.9.0.904847418882.issue29502@psf.upfronthosting.co.za>
2017-02-08 15:39:38vstinnerlinkissue29502 messages
2017-02-08 15:39:38vstinnercreate