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 terry.reedy
Recipients benjamin.peterson, eric.araujo, georg.brandl, ncoghlan, r.david.murray, rhettinger, sandro.tosi, swamiyeswanth, takayuki, terry.reedy
Date 2012-11-07.19:18:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Today in pydev thread "chained assignment weirdity" Guido said
"I agree that we should be *very* conservative in changing the
meaning of existing opcodes (adding new one is a different story)."
"Hm. I really don't think that is a good development for Python to
compromise in the area of expression evaluation order where side
effects are involved."

"I haven't looked at the proposed fixes, but I think correctness is more important than saving an extra bytecode (OTOH keeping the set of opcodes the same trumps both). I can't imagine that this extra opcode will be significant in many cases."

To which Nick C. replied
"Since you've indicated the implementation is in the wrong here and you
also want to preserve opcode semantics, I think Skip's patch is
correct, but also needs to be applied to dict comprehensions (now we
have them). The extra bytecode is only ROT_TWO, which is one of the
cheapest we have kicking around."

To which Guido said "Ok, somebody go for it! (Also please refer to my pronouncement in the bug"
Date User Action Args
2012-11-07 19:18:21terry.reedysetrecipients: + terry.reedy, georg.brandl, rhettinger, ncoghlan, benjamin.peterson, eric.araujo, r.david.murray, sandro.tosi, swamiyeswanth, takayuki
2012-11-07 19:18:21terry.reedysetmessageid: <>
2012-11-07 19:18:21terry.reedylinkissue11205 messages
2012-11-07 19:18:20terry.reedycreate