My experiences with wxPython have been very mixed; I did a small GUI App 1.5 years ago, in tk, qt, and wx (prepend Py on all of this ), and tk was (quite frankly) ugly and didn't behave, qt was unusual, and wx gave me strange errors. Tk was easiest do distribute, qt was okayish, wx was a nightmare (with/without unicode support is totally incompatible, gtk1 vs gtk2 and so on). And, after going back to the app now, I just noticed:

- the tk one still works
- the qt one gives a strange warning but still works
- the wxPy doesn't get past the imports (even after I thought I fixed them)

On reading up I noticed that there are many many negative reports regrading wx and app breakage out there. Perhaps it's better using wax?
Thomas | 06/05/06 - 1:46 am | #

Wax *possibly* abstracts away some of the API changes.

I think a combination of changes to the underlying toolkit and a big refactoring of wxPython itself caused a lot of breakages. Hopefully the current situation is more stable.

Fuzzy
Fuzzyman | Homepage | 06/05/08 - 10:55 pm | #

I came from the Java camp, so was a bit confused about the number of GUI toolkits that one can use with Python programming. Nonetheless, I've used both the tk and wx, and must say that the number of demos available for the wx made it easy for me to go with wx.

Again, wxPython in Action was a huge step forward for me as a new Python programmer.

I highly recommend it to any newbie.
Henry Dominik | Homepage | 08/05/08 - 2:55 pm | #