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 meador.inge
Recipients JelleZijlstra, benjamin.peterson, brett.cannon, georg.brandl, meador.inge, ncoghlan, yselivanov, ztane
Date 2016-05-10.02:02:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462845722.17.0.222261451109.issue26549@psf.upfronthosting.co.za>
In-reply-to
Content
Strictly speaking, the stack size is calculated *after* the peephole optimizer is run, but the code that computes the stack depth operates on the basic block graph instead of the assembled and optimized byte code.

Anyway, the conclusion is the same as Brett noted -- the stack depth analysis would need to be re-written to operate on the optimized bytecode array.
History
Date User Action Args
2016-05-10 02:02:02meador.ingesetrecipients: + meador.inge, brett.cannon, georg.brandl, ncoghlan, benjamin.peterson, yselivanov, ztane, JelleZijlstra
2016-05-10 02:02:02meador.ingesetmessageid: <1462845722.17.0.222261451109.issue26549@psf.upfronthosting.co.za>
2016-05-10 02:02:02meador.ingelinkissue26549 messages
2016-05-10 02:02:01meador.ingecreate