Dmitrijs Ledkovs [2013-03-04 23:08 +0000]: > For me the other caveats are lack of documentation look-ups, one has > to guess how it would be called in C api and look that up and then > translate to semi-pythonic dot notation, test the gi call in ipython > and only then use. > This is hardly rapid development. gtk-doc is so good, why cannot it > generate recent documentation as previously was available with pygtk? > If dbus-api gets auto-generated docs, why doesn't python?!
The current tools and autogenerated output is certainly certainly far from pretty, but it's a start: $ g-ir-doc-tool --language=Python -o /tmp/gtk /usr/share/gir-1.0/Gtk-3.0.gir $ yelp /tmp/gtk/ Or if you want HTML: $ cd /tmp/gtk $ yelp-build html . One could do that for all the gir* packages we ship whenever the package changes and stick that on a website or put the yelp XML files into a some -doc package. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel