Dave Angel wrote:
> On 03/01/2013 02:48 PM, Huperetes wrote:
> > I am getting the following for my installation.
> >
> > Why is this happening, and how do I get it to work properly (returning
> > element 0 - n, versus n - 0)?
> >
> > Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit
> I am getting the following for my installation.
>
> Why is this happening, and how do I get it to work properly (returning
> element 0 - n, versus n - 0)?
>
> Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] on
> win32
> Type "help", "copyright", "credits" or "license" fo
On 03/01/2013 02:48 PM, Huperetes wrote:
I am getting the following for my installation.
Why is this happening, and how do I get it to work properly (returning
element 0 - n, versus n - 0)?
Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)]
on win32
Type "help", "copyrigh
On Fri, Mar 1, 2013 at 2:48 PM, Huperetes wrote:
> I am getting the following for my installation.
>
> Why is this happening, and how do I get it to work properly (returning
> element 0 - n, versus n - 0)?
>
This is happening because dictionaries are not ordered. The fact that it
happens to loo
> Why is this happening, and how do I get it to work properly (returning
> element 0 - n, versus n - 0)?
Python dictionaries are unordered collections. When we iterate across
them, we can not guarantee that we'll walk the elements in the order
that we inserted them. The reason for that is becaus
I am getting the following for my installation.
Why is this happening, and how do I get it to work properly (returning
element 0 - n, versus n - 0)?
Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)]
on win32
Type "help", "copyright", "credits" or "license" for more informa