[issue45974] Using walrus produces different/unoptimized bytecode

Fatih Kilic added the comment: Ah, I see. Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45974] Using walrus produces different/unoptimized bytecode

Batuhan Taskaya added the comment: See: https://bugs.python.org/issue42282 and the reason for not backporting this: https://bugs.python.org/issue42282#msg380506 -- components: +Interpreter Core -Parser nosy: +BTaskaya resolution: -> duplicate stage: -> resolved status: open ->

[issue45974] Using walrus produces different/unoptimized bytecode

New submission from Fatih Kilic : So, what I mean by unoptimized bytecode is, for example when you type `a = 10 * 10`, the resulting bytecode is the following: ``` LOAD_CONST 0 (100) STORE_NAME 0 (a) ... ``` However, when you type, `(a := 10 * 10) == None`, the resulting bytecode is the