RetroSearch Browse

Tue Nov 6 18:58:53 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-November/122563.html

On 11/6/2012 11:26 AM, R. David Murray wrote:
> On Tue, 06 Nov 2012 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.

--Ned.

>
> --David
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/ned%40nedbatchelder.com
>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-November/122563.html below:

[Python-Dev] chained assignment weirdity