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 steven.daprano
Recipients lemburg, mark.dickinson, rhettinger, steven.daprano, stutzbach, tim.peters, vstinner
Date 2020-01-11.05:32:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree, "nextafter" is so widely used it's probably pointless to fight against the name :-)

Mark: "IEEE 754, on the other hand, requires instead nextUp and nextDown".

I know Wikipedia isn't a primary source, but it says IEEE 754 recommends nextafter(x, y).

My understanding of IEEE-754 is that the functionality is required, not the specific API. That is, it's not required to have literally two functions called "nextUp" and "nextDown", so long as you can get the next larger and next smaller float.

I think the second argument should also be optional, so that nextafter(x) returns the next representable float.
Date User Action Args
2020-01-11 05:32:29steven.dapranosetrecipients: + steven.daprano, lemburg, tim.peters, rhettinger, mark.dickinson, vstinner, stutzbach
2020-01-11 05:32:29steven.dapranosetmessageid: <>
2020-01-11 05:32:29steven.dapranolinkissue39288 messages
2020-01-11 05:32:28steven.dapranocreate