Message58768
[Guido]
> ...
> (2) Will the Windows input routine still accept the *old*
> representations for INF and NAN? IMO that's important (a) so as to be
> able to read old pickles or marshalled data, (b) so as to be able to
> read data files written by C programs.
Ha! You're such an optimist ;-) The remarkable truth is that Windows
has never been able to read its own representations for INF and NAN:
'1.#INF'
>>> float(_)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: invalid literal for float(): 1.#INF
>>> repr(nan)
'-1.#IND'
>>> float(_)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: invalid literal for float(): -1.#IND
This has nothing to do with Python -- same thing from C, etc. |
|
| Date |
User |
Action |
Args |
| 2007-12-18 20:26:10 | tim_one | set | spambayes_score: 0.278924 -> 0.278924 recipients:
+ tim_one, gvanrossum, Rhamphoryncus, christian.heimes |
| 2007-12-18 20:26:10 | tim_one | link | issue1635 messages |
| 2007-12-18 20:26:10 | tim_one | create | |
|