Tkinter Litmus Test

[rantingrick]

BPO	8971
Nosy	@merwok, @bitdancer

^{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:

assignee = None
closed_at = <Date 2010-06-11.17:40:15.906>
created_at = <Date 2010-06-11.07:27:41.018>
labels = ['expert-IDLE', 'type-feature', 'expert-tkinter']
title = 'Tkinter Litmus Test'
updated_at = <Date 2010-06-11.17:40:30.474>
user = 'https://bugs.python.org/rantingrick'

bugs.python.org fields:

activity = <Date 2010-06-11.17:40:30.474>
actor = 'eric.araujo'
assignee = 'none'
closed = True
closed_date = <Date 2010-06-11.17:40:15.906>
closer = 'eric.araujo'
components = ['IDLE', 'Tkinter']
creation = <Date 2010-06-11.07:27:41.018>
creator = 'rantingrick'
dependencies = []
files = []
hgrepos = []
issue_num = 8971
keywords = []
message_count = 2.0
messages = ['107532', '107541']
nosy_count = 3.0
nosy_names = ['eric.araujo', 'r.david.murray', 'rantingrick']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue8971'
versions = ['Python 2.7', 'Python 3.3']

[rantingrick]

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 through Python itself in form of a Warning message.

So i propose that an import warning be added to the next possible releases of Python 2.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 development team (and the wider community) your feedback on the subject. If you feel that Tkinter should or should not be removed we strongly encourage you to voice your opinion. You can do by casting your vote at "www.savetkinter.com". We need to hear everyone whether your a complete newbie or a seasoned Pythonista. Voting will end on MM-DD-YYYY so make sure your vote is counted!
"""

[bitdancer]

Everyone who uses IDLE uses TKInter, and a lot of people use IDLE.

In any case, any such proposal should be discussed on python-ideas first, followed by python-dev if you actually get a consensus about it.