This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients Rhamphoryncus, christian.heimes, gvanrossum, tim.peters
Date 2007-12-18.20:26:10
SpamBayes Score 0.2789237
Marked as misclassified No
Message-id <1f7befae0712181226pc1612fem80a332a9fcd21160@mail.gmail.com>
In-reply-to <1198007313.65.0.550878967559.issue1635@psf.upfronthosting.co.za>
Content
[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.
History
Date User Action Args
2007-12-18 20:26:10tim.peterssetspambayes_score: 0.278924 -> 0.2789237
recipients: + tim.peters, gvanrossum, Rhamphoryncus, christian.heimes
2007-12-18 20:26:10tim.peterslinkissue1635 messages
2007-12-18 20:26:10tim.peterscreate