-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Windows tcl/tk to 8.6.11 #87818
Comments
bpo-39017, PR 22405 was too late for 3.9, but the new Mac installer is already using 8.6.11. Serhiy, do you know any reason not to upgrade the Windows installer to 8.6.11 also? Steve, should a new PR with '10' replaced with '11, where '9' was replaced with '10' before, be sufficient? I presumt the 'v14' for VC13 should be left alone. To test, would 8.6.11 be built on my system, or is it fetched externally? |
I also need to pull the Tcl and Tk sources into our cpython-source-deps repository, run a signed build, and put the binaries into the cpython-bin-deps repository. I'll get that started tonight, but probably won't finish it until tomorrow. |
Turns out I did get it done, so you should be able to update the references you find in the PCbuild directory and get a build. |
Did you use revision 0, and in 8.6.11.0, or a later one? As I mentioned in bpo-43719, I cannot currently build master, but I will upload a PR (with .0) for CI to test. |
The upgrade to 8.6.10 broke a Scale test. The fix for that in bpo-41306 |
Thanks for finishing up that patch. And yes, we add a ".0" in case we need to patch the sources ourselves. |
Previous issue, which I mistyped, was bpo-39107. Release notes at |
This does not seem to have done the trick. The installers for 3.10.0 and 3.11.0a1 both use Tk 8.6.10 still. This can be verified using the bug in bpo-45681 or using |
Looks like something went wrong back when I built it in March and it built the older version again. I probably need to revamp that build step. I think it relies on a race to build properly, since it's in the main repo. We need a way to override the version it's going to build without modifying the repo, since we can't modify the repo without the build being done. |
This worked for me on main and 3.10. Thanks. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: