[issue11986] Min/max not symmetric in presence of NaN

[Raymond Hettinger]

Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The report is invalid because min/max make no guarantees about values without a total ordering.

Your other tracker item correctly focused on the behavior of float('NaN') itself, rather than on the behavior of everything else in the Python world that compares two values.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11986>
_______________________________________