This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Tkinter Litmus Test
Type: enhancement Stage:
Components: IDLE, Tkinter Versions: Python 3.3, Python 2.7
process
Status: closed Resolution: duplicate
Dependencies: Superseder: Tkinter Litmus Test
View: 8971
Assigned To: Nosy List: rantingrick
Priority: normal Keywords:

Created on 2010-06-11 07:21 by rantingrick, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (1)
msg107531 - (view) Author: Rick Johnson (rantingrick) Date: 2010-06-11 07:21
There has been much discussion in the past and recently on c.l.p about how many python programmers *actually* use Tkinter. Recently i have been involved in a lengthy discussion on c.l.p about whether or not we should remove Tkinter, replace Tkinter, or fix Tkinter. 

However i feel a decision this important cannot be made from pydev, c.l.p, or anywhere. I believe the only proper way to proceed is to get a *real* vote from *real* python programmers out in the trenches. 

But how do we do that you may ask? Well thats a good question. Not every Python programmer lives on c.l.p, or any *one* place. The only way to truly reach everyone is thru Python itself in form of a Warning message. 

So i propose that an import warning be added to the next possible releases of Python 3.x and Python 3.x. This warning will be triggered upon importing Tkinter and should also be shown when starting IDLE. The message should read loosely as follows...

"""
-------------------------------------------------
 ModuleRemovalWarning: Tkinter (and dependencies)
-------------------------------------------------
The Tkinter module (Python's GUI module) is currently being considered for removal from the python stdlib FOREVER. We are providing this warning so that you can give the python devlopment team (and the wider community) your input on the subject. If you feel that Tkinter should or should not be removed we strongly incurage you to voice your opinion. You can do by casting your vote at "www.savetkinter.com". Whether your a complete noobie or a seasoned Pythonista we need to hear everyone. Voting will end on MM-DD-YYYY, so make sure your vote is counted!
"""
History
Date User Action Args
2022-04-11 14:57:02adminsetgithub: 53216
2010-06-11 07:52:07eric.araujosetresolution: duplicate
superseder: Tkinter Litmus Test
2010-06-11 07:32:20rantingricksetstatus: open -> closed
2010-06-11 07:21:34rantingrickcreate