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 brett.cannon, dino.viehland, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-15.08:03:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481788981.54.0.907801261417.issue28924@psf.upfronthosting.co.za>
In-reply-to
Content
> It may break other debuggers like Python Tools for Visual Studio, though (+steve.dower for that).

Do you mean debuggers expecting that bytecode is run in PyEval_EvalFrameEx() rather than PyEval_EvalFrameDefault()? Can't we fix these debuggers?


> IMHO, inlining is best left to profiling optimizers.

The problem is that PGO compilation is not used by everyone yet. The patch is a minor enhancement to make sure that regular builds are also fast.
History
Date User Action Args
2016-12-15 08:03:01vstinnersetrecipients: + vstinner, brett.cannon, dino.viehland, serhiy.storchaka, steve.dower
2016-12-15 08:03:01vstinnersetmessageid: <1481788981.54.0.907801261417.issue28924@psf.upfronthosting.co.za>
2016-12-15 08:03:01vstinnerlinkissue28924 messages
2016-12-15 08:03:01vstinnercreate