➜

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 tim.peters
Recipients lemburg, mark.dickinson, rhettinger, steven.daprano, stutzbach, tim.peters, vstinner
Date 2020-01-11.05:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578721535.96.0.0435671449775.issue39288@roundup.psfhosted.org>
In-reply-to
Content 
[Steven]
> I think the second argument should also be optional, so
> that nextafter(x) returns the next representable float.

That's why the name sucks - there are, in general, two adjacent floats, so "next" is ambiguous.  I expect you intend that y default to math.inf, which would make one-argument `nextafter(x)` a spelling of `nextUp(x)`.  Fine by me!  That's probably the one I want most often.
History
Date User Action Args
2020-01-11 05:45:36tim.peterssetrecipients: + tim.peters, lemburg, rhettinger, mark.dickinson, vstinner, stutzbach, steven.daprano
2020-01-11 05:45:35tim.peterssetmessageid: <1578721535.96.0.0435671449775.issue39288@roundup.psfhosted.org>
2020-01-11 05:45:35tim.peterslinkissue39288 messages
2020-01-11 05:45:35tim.peterscreate