On Mon, Nov 9, 2009 at 2:51 PM, Terry Reedy <tjre...@udel.edu> wrote: > This also suggests to me that nan should be a singleton, or at least that > the doc should recommend that programs should make it be such for the > program.
The IEEE std disagreed -- there's extra info hidden in the mantissa bits. And the Python float implementation makes it pretty impractical to do this at the application level since x+y will generate a new NaN-valued float object each time it is called (if the outcome is NaN). -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
