Peter Azmanov

From 2cc5ce4668da32a5a2745a767cc06eecdf38e11c there shouldn't be crashes or debug breaks associated with the size of stack. P.S. Still in some cases '_compute_stacksize' returns more than needed (see [issue](https://github.com/peterazmanov/byteplay/issues/5) in my fork...

I believe current version for Python 2 (`byteplay2.py`) still containes broken stack size calculation... (original issue was reported for Python 2 version and nothing has been fixed in it) I...

I don't quite understand your improvement. The original version doesn't contain looping, it calculates stack depth for every possible scope (including loop scopes). Besides, after your changes stack depth calculation...

What do you mean by "bytecode looping"? There is no loops in your code only two possible execution branches with one label. To determine stack depth correctly one has to...