Ned Deily <n...@python.org> added the comment:
At the moment, I am holding the 3.7.2 and 3.6.8 final releases for this and another unrelated regression. I don't want to hold up these releases for all platforms just for issues related to use of Tk, tkinter, and/or IDLE on macOS. There doesn't seem to be any one really good option, though, pending real fixes or workarounds. The options I see are: 1. revert to Tcl/Tk 8.6.8 as was used with 3.7.1 and 3.6.7. At this point, I don't remember all of the problems seen with that version of Tk, though I believe one was the scrolling problem described in Issue34370. 2. continue with Tk 8.6.9.1 as shipped with 3.7.2rc1 and 3.6.8rc1. As far as a I know at the moment, the only regression there is the problem originally described in this issue, that is, windows temporarily turning black while being resized. 3. use the tip of Tk core-8-6-branch despite the problems described above. 4. look at reverting to Tcl/Tk 8.5.x and hope it works on the latest releases of macOS. (Note that the macOS Installers and the Tcl/Tk they use are built on macOS 10.9 and 10.6 depending on the installer variant.) 5. hold the release for Tk and/or tkinter and/or IDLE fixes None of those are really good options. I would rule out option 3 based on my quick tests. I don't think going to 8.5.x is a viable option at this point, either, and certainly not desirable. I really don't want to hold the release for a permanent fix or fixes unless they were likely to be available in the next 24 hours or so, since this is strictly a python.org macOS issue (although other distributors of Python and Tk on macOS will likely run into these problems). That leaves either option 1 or 2. Of the 2, at this point, I lean towards option 2 assuming no other regressions are noted, it wouldn't be the end of the world to live for awhile with the temporary black window while resizing. It's ugly but probably not as ugly as the scrolling problems that would remain with option 1. In any case, if we do go ahead and release with one of these compromises, I would document it in the release notes and would also push to release updated installers for these releases as soon as fixes are available, with the proviso that the updated installers vary from the original release installers only in Tk code and any necessary tkinter or IDLE change(s) to correct these issues, i.e. no changes in any other components in the release. Any other opinions?? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35485> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
