Jeff Epler <jepler at unpythonic.net> writes: > [I apologize that I'm not adding this information to the bug report, but > I'm not able to log into SF right now, the login page hangs while loading] > >> 1==float('nan') (2004-02-17) >> http://python.org/sf/899109 opened by Arman Bostani > > I'm sure Tim can explain this better, but what happens is this: 1 is > coerced to float for comparison. Then, the following C expression is > evaluated (Objects/floatobject.c:float_compare): > return (i < j) ? -1 : (i > j) ? 1 : 0; Would it make (more) sense to implement rich comparisons for floats? I'm not enthusiastic about the patch that got pasted into the bug report. Cheers, mwh -- [1]For those of you who aren't aware "tossing" is a euphamism for, well, vigourously rubbing your love pole. You understand? Flogging the dolphin. Stretching the chicken's neck. Waving your magic wand. Basically, wanking. -- Just another Morfans SDA update
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4