[issue1732212] repr of 'nan' floats not parseable

2009-02-10 Thread Martin v. Löwis

Changes by Martin v. Löwis :


--
resolution:  -> rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1732212] repr of 'nan' floats not parseable

2009-02-10 Thread Raymond Hettinger

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 about it seems like a
reasonable workaround.

IMO, the special case code we've already added to support NaNs and Infs
has already far exceeded their worth in real-world use cases.  No need
to further muddy the waters when simple workarounds exist.

--
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1732212] repr of 'nan' floats not parseable

2009-02-10 Thread Mark Dickinson

Changes by Mark Dickinson :


--
assignee:  -> marketdickinson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1732212] repr of 'nan' floats not parseable

2009-02-10 Thread Mark Dickinson

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 of a 
container with nans in it.  But in 
that situation it's not hard to prefix the eval with "nan = float('nan'); inf = 
float('inf')".

Pete, are you still interested in this?  Can you suggest a solution that 
doesn't mess up the float(repr(.)) round-
trip?  I don't really want to lose the float(repr(.)) round-trip.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1732212] repr of 'nan' floats not parseable

2009-02-10 Thread Daniel Diniz

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1732212] repr of 'nan' floats not parseable

2008-01-05 Thread Christian Heimes

Changes by Christian Heimes:


--
priority: normal -> low
type:  -> rfe
versions: +Python 2.6

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com