diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2022-09-01 19:23:27 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-01 19:23:27 (GMT) |
| commit | bb8e49b4203fc1f2df554b452dbd3926102b18ee (patch) | |
| tree | fdc6bd5323f879264a25988d2ac55403aab084b8 /Python/pythonrun.c | |
| parent | c19983125a42a4b4958b11a26ab5e03752c956fc (diff) | |
| download | cpython-bb8e49b4203fc1f2df554b452dbd3926102b18ee.zip cpython-bb8e49b4203fc1f2df554b452dbd3926102b18ee.tar.gz cpython-bb8e49b4203fc1f2df554b452dbd3926102b18ee.tar.bz2 | |
bpo-41306: Allow scale value to not be rounded (GH-21715) (GH-96484)
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 'Python/pythonrun.c')
0 files changed, 0 insertions, 0 deletions