homepage

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 larry
Recipients benjamin.peterson, eric.snow, larry, ncoghlan, serhiy.storchaka
Date 2018年01月04日.00:14:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515024844.24.0.467229070634.issue32455@psf.upfronthosting.co.za>
In-reply-to
Content
The rationale: without this information, it is impossible for anybody else to write a bytecode compiler / assembler, because when you create a code object you have to specify its stack depth. I used this information for my "maynard" bytecode assembler / disassembler.
That said, I'm not sure who needs these super-fancy versions Serhiy is proposing. To calculate stack depth, all you really need is the *maximum* stack depth per instruction. You might slightly over-allocate but it shouldn't really be much of a problem.
Serhiy: what's your use case for all these complicated new features?
History
Date User Action Args
2018年01月04日 00:14:04larrysetrecipients: + larry, ncoghlan, benjamin.peterson, eric.snow, serhiy.storchaka
2018年01月04日 00:14:04larrysetmessageid: <1515024844.24.0.467229070634.issue32455@psf.upfronthosting.co.za>
2018年01月04日 00:14:04larrylinkissue32455 messages
2018年01月04日 00:14:04larrycreate

AltStyle によって変換されたページ (->オリジナル) /