>> It's not a matter of dependence on iteration order, but of
>> reproducibility (in my case there were minor numerical differences due
>> to different iteration orders).
>
> Can you give a code example? I don’t understand your case.
It's a bit involved (that's why it took me a while to locate t
On Feb 26, 2011, at 4:09 PM, Antoine Pitrou wrote:
> On Sat, 26 Feb 2011 10:09:33 +0100
> Hagen Fürstenau wrote:
>>
>> I just hunted down a change in behaviour between Python 3.1 and 3.2 to
>> possibly changed iteration order of sets due to the optimization in
>> issue #8685. Of course, this or
On Sat, 26 Feb 2011 10:09:33 +0100
Hagen Fürstenau wrote:
>
> I just hunted down a change in behaviour between Python 3.1 and 3.2 to
> possibly changed iteration order of sets due to the optimization in
> issue #8685. Of course, this order shouldn't be relied on in the first
> place, but the side
Hagen Fürstenau wrote:
Code with any dependence on the iteration order of unordered collections
(other than the guarantee that d.keys() and d.values() match at any
given time as long as d is unchanged) is buggy.
It's not a matter of dependence on iteration order, but of
reproducibility (in my c
> It's not a matter of dependence on iteration order, but of
> reproducibility (in my case there were minor numerical differences due
> to different iteration orders).
Can you give a code example? I don’t understand your case.
Regards
___
Python-Dev ma
> Code with any dependence on the iteration order of unordered collections
> (other than the guarantee that d.keys() and d.values() match at any
> given time as long as d is unchanged) is buggy.
It's not a matter of dependence on iteration order, but of
reproducibility (in my case there were minor
On 2/26/2011 4:09 AM, Hagen Fürstenau wrote:
Hi,
I just hunted down a change in behaviour between Python 3.1 and 3.2 to
possibly changed iteration order of sets due to the optimization in
issue #8685. Of course, this order shouldn't be relied on in the first
place, but the side effect of the opt
Hi,
I just hunted down a change in behaviour between Python 3.1 and 3.2 to
possibly changed iteration order of sets due to the optimization in
issue #8685. Of course, this order shouldn't be relied on in the first
place, but the side effect of the optimization might be worth mentioning
in "What's
