Message75747
| Author |
mark.dickinson |
| Recipients |
barry, christian.heimes, gvanrossum, mark.dickinson, mikecurtis, rhettinger |
| Date |
2008年11月11日.16:44:53 |
| SpamBayes Score |
6.2394534e-14 |
| Marked as misclassified |
No |
| Message-id |
<1226421894.57.0.879652277509.issue4296@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
[Michael]
> the real issue that caused problems [...] was Python deciding to
> silently cast NaN falues to 0L
> [...]
> it sounds like there is no intention to fix this for versions prior
> to 3.0,
Oh, <rude words> <rude words> <more rude words>! Guido's message does
indeed say that that behaviour shouldn't be changed before 3.0. And
if I'd managed to notice his message, I wouldn't have 'fixed' it for
2.6.
Python 2.7a0 (trunk:67115, Nov 6 2008, 08:37:21)
[GCC 4.0.1 (Apple Inc. build 5488)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> int(float('nan'))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: cannot convert float NaN to integer
:-(.
[Imagine me looking extreeemely sheepish.]
I guess I owe apologies to Christian and Guido here. Sorry, folks. Is
there any way I can make amends? |
|