-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Remove deprecated tkinter.tix module #75552
Comments
Tix is an old Tk widget extension set that has long been superseded by the ttk widgets that were added in Tk 8.5, officially released 10 years ago and since superseded by Tk 8.6. Tix was useful for users of Tk 8.4 but tkinter is no longer built, tested, or supported with 8.4. Despite that, we have continued to build and ship Tix with the python.org Windows installers. The last maintenance release of Tix was in 2008. As of Python 3.6.0 (https://docs.python.org/3.6/library/tkinter.tix.html), we documented tkinter.tix as: Deprecated since version 3.6: This Tk extension is unmaintained For 3.7, I believe it is time to remove both tkinter.tix and the building of Tix in the Windows builds. |
+1 for removal. |
According to PEP-4, "In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP-373." Is there a reason for haste? The Tix library still is included in recent versions of Linux distributives and should be compatible with Tcl 8.6. Ttk is not direct replacement of Tix. They provide different sets of widgets. May be you meant Tile, the predecessor of ttk? |
We should decide on this. I agree with Serhiy that in accordance with PEP-4, as long as Tix still works, we should keep it. |
We missed the boat for 3.7 anyway. With the PEP-4 argument, I won't push any further for ripping Tix out completely before 2020, but if something happens to break building it on Windows before then my fix will be to remove it from the Windows build. |
For anyone looking for more details on the reasoning behind this removal, @zware's comment on the PR explains this well:
|
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:
Linked PRs
The text was updated successfully, but these errors were encountered: