Mark Dickinson <dicki...@gmail.com> added the comment:
This isn't a bug in Python; it's a consequence of the what-you-see-is-not-what-you-get nature of binary floating-point. The behaviour is explained in the tutorial, here: https://docs.python.org/3/tutorial/floatingpoint.html ---------- nosy: +mark.dickinson resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41057> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
