Josiah Carlson wrote: > Also, it would require shipping a Python GTK binding, which would > basically necessitate shipping GTK+ with Python.
Keep in mind that PyGUI is still very much a work in progress. My eventual goal is for each implementation to depend only on what is provided natively by the platform. The use of the Gtk implementation on Windows is only a stopgap measure until something more native is available. I'd like to see PyGUI or something like it become more widely used and maybe even included in the core one day, but it needs a lot more development first. Whether it will have reached a sufficient level of development by the time Py3k comes around remains to be seen. > we may as well go whole hog and take wxPython; I'd be disappointed if something like wxPython were chosen as the next "official" Python gui, for a lot of reasons -- bloat, ugly and unpythonic API, non-native appearance and behaviour, dubious quality of ports, etc. > and it offers an "upgrade" path towards more "Pythonic" > additions like Pythoncard, Wax, or even Dabo. I'm also not fond of the idea of putting yet more layers of code over something that's already too bloated. -- Greg _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
