Raymond Hettinger <[email protected]> added the comment:
> The performance thoughts were motivated by the idea of
> making NaN a singleton: adding a check to
> PyFloat_FromDouble would mean that almost every operation
> that produced a float would have to pass through that check.
It may suffice to move the check upstream from PyFloat_FromDouble so that
float('NaN') alway produces identically the same object as math.nan.
That would handle the common cases where NaN is used for missing values or is
generated from string conversions. We don't need a bullet-proof solution, just
mitigation of harm.
----------
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue43475>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
