This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Dennis Sweeney, joel.larose, mark.dickinson, serhiy.storchaka, steven.daprano
Date 2021-06-10.18:29:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623349786.57.0.282829849738.issue44370@roundup.psfhosted.org>
In-reply-to
Content
The idea of math.ieee754_total_order looks interesting, but how would it work with min/max?

In https://grouper.ieee.org/groups/msc/ANSI_IEEE-Std-754-2019/background/minNum_maxNum_Removal_Demotion_v3.pdf there is a comparison of several standards and implementations of symmetric and associative min/max. There are two options: propagate NaN and ignore it (treat it as missing data). It differs between different standards and implementations but in particular standard or implementation the same rule is used for min and max.

* If ieee754_total_order(NAN) < ieee754_total_order(1), then min(1, NAN) -> NAN ("propagate") and max(1, NAN) -> 1 ("missing data").
* If ieee754_total_order(NAN) > ieee754_total_order(1), then min(1, NAN) -> 1 ("missing data") and max(1, NAN) -> NAN ("propagate").
History
Date User Action Args
2021-06-10 18:29:46serhiy.storchakasetrecipients: + serhiy.storchaka, mark.dickinson, steven.daprano, Dennis Sweeney, joel.larose
2021-06-10 18:29:46serhiy.storchakasetmessageid: <1623349786.57.0.282829849738.issue44370@roundup.psfhosted.org>
2021-06-10 18:29:46serhiy.storchakalinkissue44370 messages
2021-06-10 18:29:46serhiy.storchakacreate