On Sat, Jun 18, 2016 at 11:32:52PM +0100, Obiesie ike-nwosu via Python-Dev
wrote:
> That is much clearer now.
> Thanks a lot Raymond for taking the time out to explain this to me.
> On a closing note, is this mailing list the right place to ask these kinds
> of n00b questions?
That depends wha
That is much clearer now.
Thanks a lot Raymond for taking the time out to explain this to me.
On a closing note, is this mailing list the right place to ask these kinds of
n00b questions?
Obi.
> On 18 Jun 2016, at 23:10, Raymond Hettinger
> wrote:
>
>
>> On Jun 18, 2016, at 2:04 PM, Obiesie
> On Jun 18, 2016, at 2:04 PM, Obiesie ike-nwosu via Python-Dev
> wrote:
>
> Hi,
>
> Could some one give a hand with explaining to me why we have a JUMP_ABSOLUTE
> followed by a JUMP_FORWARD op code when this function is disassembled.
> < snipped>
> From my understanding, once JUMP_ABSOLUTE
Python has a peephole optimizer which does not remove dead code that it
just created.
Victor
Le 18 juin 2016 23:14, "Obiesie ike-nwosu via Python-Dev" <
python-dev@python.org> a écrit :
> Hi,
>
> Could some one give a hand with explaining to me why we have a
> JUMP_ABSOLUTE followed by a JUMP_FOR
Hi,
Could some one give a hand with explaining to me why we have a JUMP_ABSOLUTE
followed by a JUMP_FORWARD op code when this function is disassembled.
>>> def f1():
... a, b = 10, 11
... if a >= 10:
... if b >= 11:
... print("hello world")
…
The disass
