You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can not use Tkinter in the version of 3.13.0, even if I just import tkinter will have a wrong. I try to run the program on two different laptops, and have the same problem.
from tkinter import *
Process finished with exit code -1073741819 (0xC0000005)
### CPython versions tested on:
3.13
### Operating systems tested on:
Windows
Also worth noting that I ran into this issue with the binary from the python.org installer as well as installing Python via UV.
My python.org-installed version is installed for just my user, and I do see the above-mentioned init.tcl file in C:\Users\MY_USER_NAME\AppData\Local\Programs\Python\Python313\tcl\tcl8.6 but this directory is not listed in the traceback as one of the ones being searched.
Reacted by bersbersbers, ogiarch and Seppe Van Bogaert
I download the installer from the official site.I test again on Windows 11, If I install with the option clicked, it will have this problem. If I install without download free-threaded binaries, tkinter can run normally.
Activity
terryjreedy commentedon Oct 9, 2024
Works fine for me when installed with the new python.org installer.
Please give exact details of how you got your python binary and exact how you ran it.
Note: the triple backticks should enclose code and output but not the template headings and responses.
[-]Tkinter can not use in the version of 3.13.0[/-][+]Tkinter does not run in 3.13.0[/+]colesbury commentedon Oct 9, 2024
Did you install the free-threaded binaries? Tkinter is broken on free-threaded Windows 3.13t: #118973
terryjreedy commentedon Oct 9, 2024
I have been running IDLE on locally built free-threading builds since March 15 this year, so this is a packaging issue.
joshburnett commentedon Oct 9, 2024
I see this issue when running Python from within a venv:
Running in the base Python install works OK. I'm not running the free-threaded build.
I'm testing on Windows 11, though I've seen a report of this on Windows 10 as well.
Also worth noting that I ran into this issue with the binary from the python.org installer as well as installing Python via UV.
My python.org-installed version is installed for just my user, and I do see the above-mentioned
init.tclfile inC:\Users\MY_USER_NAME\AppData\Local\Programs\Python\Python313\tcl\tcl8.6but this directory is not listed in the traceback as one of the ones being searched.litiegang1989 commentedon Oct 10, 2024
I download the installer from the official site.I test again on Windows 11, If I install with the option clicked, it will have this problem. If I install without download free-threaded binaries, tkinter can run normally.
terryjreedy commentedon Oct 10, 2024
@joshburnett Please open a separate issue for failures, if any, that only occur with venv. Reference threads on discuss.python.org if this is claimed.
EDIT: Robin Becker opened #125235. Fix in 3.13.1.