Linked by Amjith Ramanujam on Tue 5th Aug 2008 16:48 UTC
General Development Computerworld is undertaking a series of investigations into the most widely-used programming languages. This time we chat with Guido van Rossum, best known as the author of Python, and currently working for Google, CA where he gets to spend at least half his time developing the language.
Thread beginning with comment 325796
To read all comments associated with this story, please click here.
New GUI Toolkit needed for Python
by Coral Snake on Wed 6th Aug 2008 02:16 UTC
Coral Snake
Member since:

Actually the only thing I see wrong with Python is that it still ships with the Tkinter GUI toolkit as its standard for GUIs. This toolkit is obsolete in two ways, the first being its Motif look under Linux and BSD based platforms using x11 and the second being its virtually Windows 3.x widget choice and functionality. Yet another problem with Tkinter is that it requires the running of TWO programming language interpreters (both TK and Python) for GUI programs making it slower than managed languages having their own GUI toolkits like Java/Swing and C#/Forms.

What Python needs in the GUI area is either a toolkit coded in Python itself with modern widget design, choice and functionality so that only one interpreter/managed environment is needed to run them ala Java/Swing and C#/Forms or shipping with one of the popular C++ toolkits used with Python probably wxWidgets/wxPython rather than the obsolete and second interpreter dependent Tkinter.

Reply Score: 2

Clinton Member since:

I completely agree. I personally like PyQt better than wxPython, but either one would be a huge improvement over Tk.

Reply Parent Score: 2

Coral Snake Member since:

I think it would have to be a native python toolkit or wxPython because I believe that the python developers want Python available to Proprietary and F/OSS software on an equal basis. The high prices for QT licenses would proclude this if pyQT were used as the shipping GUI library for Python. however wxWidgets does have a pretty complete and modern widget set. (Only drag and drop and tool tips are missing from the wxUniversal x11 based version of wxwidgets which is probably the one that should be used with *nix based python distributions to prevent GTK dependency conflicts between Linux and BSD distributions. These conflicts are also present with QT
with people running version 2, 3 and 4 software these days depending on the power of their computers.

Edited 2008-08-06 06:29 UTC

Reply Parent Score: 2

Soulbender Member since:

Actually the only thing I see wrong with Python is that it still ships with the Tkinter GUI toolkit as its standard for GUIs

Define "ships with". Tk is optional and you don't have to install it.
Also, how many apps today actually uses Tk? If you don't like it just use PyGTK, PyQT, wxPython or whatever and move on.

Reply Parent Score: 2

sanctus Member since:

wxWindow is horribly slow on OS X and Linux.

pyQT has it licensing issue.

pyGTK is not cross platform. In OS X you need X11 and it's painfully ugly. In windows it look better yet, but still awkward.

Sure these are good toolkit. But there's no clear winner.

Reply Parent Score: 2

ameasures Member since:

There was an ANYGUI toolkit (AFAIR) but I think it lost momentum.

Frankly it is a shame that there isn't a standard cross platform GUI toolkit for Python. A great opportunity missed in my book.

Jython and Swing have tempted me in the past but never enough to do anything about it!


Reply Parent Score: 2