Mark Dickinson <dicki...@gmail.com> added the comment: > This change was advertised in the "What’s New In Python 3.0" document.
Not originally, it wasn't. That information was added later, by me. :-) [1] In any case, I wasn't referring to documentation. I meant "silent" in the runtime-sense: there was no run-time error or warning associated with the behaviour change (in contrast to the `print` function change, for example). Few people read the "what's new" documents, and someone who's written Python 2 code using round has no particular reason to suspect a behaviour change, and no visible indication that such a change has occurred, when porting their code to Python 3. Nevertheless, their numerical results may be slightly different as a result of the porting. Hence the potential for late-discovered bugs. [1] https://github.com/python/cpython/commit/f4112e2653f310b6e6a210c659648dbe45d3a042 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32956> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
