Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #74200 > unrolled thread
| Started by | "Anders J. Munch" <2014@jmunch.dk> |
|---|---|
| First post | 2014-07-08 20:54 +0200 |
| Last post | 2014-07-08 20:54 +0200 |
| 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: NaN comparisons - Call For Anecdotes "Anders J. Munch" <2014@jmunch.dk> - 2014-07-08 20:54 +0200
| From | "Anders J. Munch" <2014@jmunch.dk> |
|---|---|
| Date | 2014-07-08 20:54 +0200 |
| Subject | Re: NaN comparisons - Call For Anecdotes |
| Message-ID | <mailman.11652.1404845648.18130.python-list@python.org> |
Ian Kelly wrote: > As far as I know nothing changed between 2.4 and 2.7 in this regard. > Python has always had NaN compare unequal to everything, per the > standard. It might have been platform-specific in 2.4. > Okay, here's your problem: there isn't just one binary representation > for NaN. I'm fully aware of that. Whether NaN's are one equivalence class or several is not the issue. What matters is the integrity of the equivalence relation. > Following the standard isn't a good reason itself? If a standard tells you to jump of a cliff... regards, Anders
Back to top | Article view | comp.lang.python
csiph-web