Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #30501 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2012-09-30 00:25 +1000 |
| Last post | 2012-09-30 00:25 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RELEASED] Python 3.3.0 Chris Angelico <rosuav@gmail.com> - 2012-09-30 00:25 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-09-30 00:25 +1000 |
| Subject | Re: [RELEASED] Python 3.3.0 |
| Message-ID | <mailman.1634.1348928706.27098.python-list@python.org> |
On Sun, Sep 30, 2012 at 12:17 AM, Stefan Behnel <stefan_ml@behnel.de> wrote: > Christian Heimes, 29.09.2012 16:06: >> From now on you can't rely >> on the order of an unordered type like dict or set. > > Tautologies tend to be true even without a temporal qualification. Technically people shouldn't ever have relied on the order, but until hash randomization came in, the order in CPython was actually predictable - for a given set of dictionary operations, the internal structure was determinate, and the consequent iteration order would be consistent. Now that that's no longer the case, "unordered" really means "unordered", and the order can change from one run of a program to another. So it may be a tautology in theory, but not in practice..... until now. Truth has become true. ChrisA
Back to top | Article view | comp.lang.python
csiph-web