On Nov 6, 2012 1:05 PM, "Ned Batchelder" <ned at nedbatchelder.com> wrote: >> On 11/6/2012 11:26 AM, R. David Murray wrote: >>>> On 2012年11月06日 18:14:38 +0200, Serhiy Storchaka <storchaka at gmail.com> wrote: >>>>>> Another counterintuitive (and possible wrong) example: >>>>>> >>> {print('foo'): print('bar')} >>> bar >>> foo >>> {None: None} >>>> http://bugs.python.org/issue11205 >>> This seems to me better left undefined, since there's hardly ever a need to know the precise evaluation sequence between keys and values, and retaining some amount of "unspecified" to allow for implementation flexibility is a good thing. "Left undefined"? The behavior was defined, but CPython didn't follow the defined behaviour. --Devin (phone) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20121106/3f9e0091/attachment.html>