diff options
author | Miss Skeleton (bot) <31488909+miss-islington@users.noreply.github.com> | 2020-10-08 16:14:33 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-10-08 16:14:33 (GMT) |
commit | 3d103e06951324680c587d4fe1135f06367c9d3d (patch) | |
tree | abc39acabe4d81b1744d2955a87ce9e5232ee260 /Lib/tkinter/test/test_tkinter/test_misc.py | |
parent | 6c6c256df3636ff6f6136820afaefa5a10a3ac33 (diff) | |
download | cpython-3d103e06951324680c587d4fe1135f06367c9d3d.zip cpython-3d103e06951324680c587d4fe1135f06367c9d3d.tar.gz cpython-3d103e06951324680c587d4fe1135f06367c9d3d.tar.bz2 |
bpo-41306: Allow scale value to not be rounded (GH-21715)
This fixes the test failure with Tk 6.8.10 which is caused by changes to how Tk rounds the `from`, `to` and `tickinterval` arguments. This PR uses `noconv` if the patchlevel is greater than or equal to 8.6.10 (credit to Serhiy for this idea as it is much simpler than what I previously proposed).
Going into more detail for those who want it, the Tk change was made in [commit 591f68c](https://github.com/tcltk/tk/commit/591f68cb382525b72664c6fecaab87742b6cc87a) and means that the arguments listed above are rounded relative to the value of `from`. However, when rounding the `from` argument ([line 623](https://github.com/tcltk/tk/blob/591f68cb382525b72664c6fecaab87742b6cc87a/generic/tkScale.cGH-L623)), it is rounded relative to itself (i.e. rounding `0`) and therefore the assigned value for `from` is always what is given (no matter what values of `from` and `resolution`).
Automerge-Triggered-By: @pablogsal
(cherry picked from commit aecf036738a404371303e770f4ce4fd9f7d43de7)
Co-authored-by: E-Paine <63801254+E-Paine@users.noreply.github.com>
Diffstat (limited to 'Lib/tkinter/test/test_tkinter/test_misc.py')
0 files changed, 0 insertions, 0 deletions