➜

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 barry
Recipients Arfrever, Mark.Shannon, PaulMcMillan, Zhiping.Deng, alex, barry, benjamin.peterson, christian.heimes, dmalcolm, eric.araujo, georg.brandl, gvanrossum, jcea, pitrou, terry.reedy, vstinner
Date 2012-01-04.15:08:36
SpamBayes Score 7.883485e-05
Marked as misclassified No
Message-id <20120104100832.00e0e5a3@limelight.wooz.org>
In-reply-to <1325656838.58.0.858793240155.issue13703@psf.upfronthosting.co.za>
Content 
On Jan 04, 2012, at 06:00 AM, Paul McMillan wrote:

>Developers would be startled to find that ordering stays consistent on a 64
>bit build but varies on 32 bit builds.

Well, one positive outcome of this issue is that users will finally viscerally
understand that dictionary (and set) order should never be relied upon, even
between successive runs of the same Python executable.
History
Date User Action Args
2012-01-04 15:08:37barrysetrecipients: + barry, gvanrossum, georg.brandl, terry.reedy, jcea, pitrou, vstinner, christian.heimes, benjamin.peterson, eric.araujo, Arfrever, alex, dmalcolm, Mark.Shannon, Zhiping.Deng, PaulMcMillan
2012-01-04 15:08:36barrylinkissue13703 messages
2012-01-04 15:08:36barrycreate