gui toolkits: the real story? (Tkinter, PyGTK, etc.)

Terry Reedy tjreedy at udel.edu
Tue Oct 2 16:22:22 CEST 2007


"bramble" <cadet.bramble at gmail.com> wrote in message 
news:1191293650.355504.312590 at n39g2000hsh.googlegroups.com...
| I don't know... As I meant to imply above, it's looking like Tkinter
| will be playing its expected role in Py3k as the GUI toolkit of
| choice. And from what I've seen of the Py3k effort, there's been
| really excellent work on pulling out stuff that should be pulled out.
| So, if it was *really* simply only first-mover advantage keeping it
| there, I'd expect to see talk of removing it from the standard
| library.

First, the 3.0a1 release put off modification of the stdlib.  Second, Guido 
wants to distribute a minimal development environment - Idle - and that is 
written in TKinter.  Third, I have not seen a formal proposal from the 
authors of any other GUI toolkit that such replace TKinter or even 
supplement it.  There are disadvantages as well as advantages to having 
one's work in the stdlib.






More information about the Python-list mailing list