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 David.Edelsohn
Recipients David.Edelsohn, Michael.Felt, lemburg, mark.dickinson, rhettinger, stutzbach, vstinner
Date 2020-11-16.15:22:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605540151.03.0.552655934996.issue42323@roundup.psfhosted.org>
In-reply-to
Content
I investigated another problem with nextafter() in 2015 and opened an internal IBM AIX PMR.  At the time it was not using decimal float code.

The earlier problem was the handling of -0.0.  At the time, the code was hand-written assembly language that did not check for IEEE floating point corner cases.
History
Date User Action Args
2020-11-16 15:22:31David.Edelsohnsetrecipients: + David.Edelsohn, lemburg, rhettinger, mark.dickinson, vstinner, stutzbach, Michael.Felt
2020-11-16 15:22:31David.Edelsohnsetmessageid: <1605540151.03.0.552655934996.issue42323@roundup.psfhosted.org>
2020-11-16 15:22:31David.Edelsohnlinkissue42323 messages
2020-11-16 15:22:30David.Edelsohncreate