Tkinter import sometimes fails in 3.13.0

[noblockhit]

The failiure of the tkinter import on 3.13.0 is still undocumented / not mentioned in the patch notes of 3.13.1 or even better: the download option here:
https://www.python.org/downloads/#:~:text=Release%20Notes-,Python%203.13.0,-Oct.%207%2C%202024
should be repackaged, so that tkinter actuall works.

[picnixz]

Please add more details. What is the error? what are you trying to do? what is missing exactly? which operating system are you using?

[noblockhit]

Sorry, clicked enter too early, post was edited to the intended content.

[picnixz]

My question remains: what is the exact issue? when you say "cannot import tkinter", is it just import tkinter that is failing? how are you building Python? what is your operating system?

[noblockhit]

As mentioned here: #125235 The tkinter library was improperly packaged or something alike on 3.13.0. For me, it also fails when importing tkinter regularly in a free threaded environment. I get no error message, python just silently quits when i try importing tkinter like this: import tkinter. I did not compile python myself, i just downloaded it from the link i pasted in the post body.

[picnixz]

Have you tried downloading 3.13.1 instead of 3.13.0 (https://www.python.org/downloads/release/python-3131/)? if there's a bug in a previous version, we don't re-upload a corrected version.

[noblockhit]

Yes I did, but I am having trouble installing other 3rd party modules like rawpy and opencv-python because there are either no compatible versions yet, or deprecated functions in use like ImpImporter from pkgutils in the case of opencv-python

[picnixz]

I'm afraid we can't do anything. We may perhaps try to see if we can include it in 3.13.0 and republish it but this is left to the RM @Yhg1s. I think this needs to be closed as wont fix unfortunately =/

The best shot for you is to use 3.12.X instead.

[Yhg1s]

Yes, there's nothing we can do for 3.13.0. The fix is in 3.13.1. If something is stopping you from using 3.13.1 instead of 3.13.0, that's a separate issue that should be looked at (but that wouldn't change the fact that we cannot retroactively fix 3.13.0.)