Message326613
> 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 |
|
Date |
User |
Action |
Args |
2018-09-28 07:09:02 | mark.dickinson | set | recipients:
+ mark.dickinson, tim.peters, vstinner, jyasskin, ezio.melotti, njs, jab, serhiy.storchaka, MJH |
2018-09-28 07:09:02 | mark.dickinson | set | messageid: <1538118542.11.0.545547206417.issue32956@psf.upfronthosting.co.za> |
2018-09-28 07:09:02 | mark.dickinson | link | issue32956 messages |
2018-09-28 07:09:01 | mark.dickinson | create | |
|