Raymond Hettinger <rhettin...@users.sourceforge.net> 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 <rep...@bugs.python.org>
<http://bugs.python.org/issue1732212>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
