great breakdown, and i personally hate the idea of this being incorporated to Python,(reply>), @ns d1 The "number of wtf" goes exponentially down the longer it is in place. It is a way to easily assign a value and use it immediately on the fly, we aren't talking something intensely complex here. Once people get used to it and understand its function (and it isn't hard to grasp imo), it'll easily flow along just like list comprehensions. You could say the same thing about += and other similar assignment operators; is it not more "dumb clean" to instead write   &gt;&gt;&gt; var += 1   over   &gt;&gt;&gt; var = var + 1  ? I don't think the walrus operator makes code less "dumb clean", rather it cleans up a lot of operations that can (and should be) condensed, just like += did.,(reply>), @ns d1 Yes! Your first paragraph - Yes!  Your first sentence, which is worth repeating: "imho production code should be dumb clean." - Yes!! People who pay for code will rue the introduction of the walrus operator. If they're sensible, production coders  will eschew it, and if the walrus operator is used widely and almost certainly mysteriously, Python's utility and consequent use in production will be diminished.,(reply>), ​@Science Compliance imho production code should be dumb clean. if few months down the line you need to re-read your (or someone's) code and you (someone) needs to apply extra efforts (parse though syntax sugar) to understand what's going  then such shenangigans have negative added value.   // hello uncle bob;  <br><br>&gt; How do you feel about list comprehensions?  What about decorators?<br>it depends how complicated /these things are ... <br><br>on walrus - just the fact that you can assign value to a variable while evaluating expression in if / else is creepy.. recipe for disastrous bugs.<br><br>there is a good metric on the quality of the code - "number of wtf per minute", so imho walrus will be a top contributor<br><br>^^ all this above is just  my personal opinion formed from experience. i might be wrong.,(reply>), @five seven a function would not work in this case, semantically,(reply>), @ns d1 Are there not other similar 'shenanigans' in Python?  How do you feel about list comprehensions?  What about decorators?