Michael Torrie <torr...@gmail.com> wrote: > On 07/30/2018 11:04 AM, Akkana Peck wrote: > > Yes, this is the future, since it lets you use both GTK3 and Python3. > > Unfortunately the automatically-generated bindings, while fast and > complete, are not quite as pythonic as the old PyGTK bindings were. The > abstraction layer pygobject provides leaks some of the underlying C-isms > through. I can't remember exactly which bits feel the most foreign as > it's been a while since I used it. But who am I kidding? PyQt (my > preferred toolkit) or PySide aren't terribly Pythonic either; lots of > C++ and Qt abstractions leaking through various Qt types when native > Python types would be preferable (like lists and dictionaries).
Yes, this has been some of my problem when starting to use these packages. I'm a retired Software Engineer and I spent much of my career (like the last 40 years or more) writing C/C++, so seeing C-like code isn't 'difficult', but it can be confusing. Some of the bits of 'example' code are actually C/C++ rather than Python which had me very confused for a while! Also there's the oddity of Gtk.Window and Gtk.Window.new (also due to the C/C++ ancestry?). -- Chris Green ยท -- https://mail.python.org/mailman/listinfo/python-list
