[issue1732212] repr of 'nan' floats not parseable

Changes by Martin v. Löwis : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue1732212] repr of 'nan' floats not parseable

Raymond Hettinger added the comment: Recommend closing this. We like to have eval(repr(obj))==obj where possible but it is not a strict requirement. Am opposed to the two proposed solutions (float attributes or new literals). Mark's solution of defining nan=float('nan') whereever you care abo

[issue1732212] repr of 'nan' floats not parseable

Changes by Mark Dickinson : -- assignee: -> marketdickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1732212] repr of 'nan' floats not parseable

Mark Dickinson added the comment: I don't see a huge need for this. In 2.6, 3.0 and higher, float(repr(x)) recovers x reliably across platforms (modulo the occasional system strtod bug), even when x is an infinity or nan. It's true that using float() doesn't help if you want to eval the repr

[issue1732212] repr of 'nan' floats not parseable

Daniel Diniz added the comment: OP posted a message in python-dev, with no replies: http://mail.python.org/pipermail/python-dev/2007-June/073625.html -- nosy: +ajaksu2, marketdickinson versions: +Python 2.7, Python 3.1 -Python 2.6 ___ Python tracker

[issue1732212] repr of 'nan' floats not parseable

Changes by Christian Heimes: -- priority: normal -> low type: -> rfe versions: +Python 2.6 _ Tracker <[EMAIL PROTECTED]> _ ___ Pytho