Skip to main content


Embloggeration happened, in which I look at the state of the #Python bindings for the #GNOME platform

https://www.bassi.io/articles/2022/12/02/on-pygobject/

If you like Python, and you want to use #GTK to write your applications, please consider joining the effort to maintain the PyGObject bindings.

reshared this

Unknown parent

Emmanuele Bassi
@shanefagan lazka does the reviews, when he has time; I can also help out a bit. Trading reviews is something that would help, actually: you can do triage and initial reviews, and verify that contributions are correct even without pressing the "Merge" button. Having a third party confirmation would reduce the maintainer workload.
Unknown parent

Shane Fagan
Actually on that line, who is reviewing pull requests? There are a few built up it looks like. Would it be a good idea to go through those first?
Unknown parent

Emmanuele Bassi
@shanefagan Thanks! That'd be very much appreciated
in reply to Emmanuele Bassi

I made the GTK4 docs for pygobject. Happy to help out.
in reply to Emmanuele Bassi

It seems logical to build on your work for documentation generation. Would that work for PyGObject?
in reply to Arjan

@amolenaar The current documentation generator for C is based on pygobject's own 🙂 Having the introspection data and docs be the shared source of "truth" for doc generators benefits every language. Ideally, pgi-docgen should be fixed to parse the new gi-docgen "smart" links to allow cross-linking.

From a hosting perspective, being able to build the Python docs on GNOME infrastructure would be great: more people would be able to work on it and keep it up to date.
in reply to Emmanuele Bassi

@amolenaar As for developers docs, making sure that the tutorials and examples on developer.gnome.org work properly with pygobject would be great. Right now, I'm the only person doing that, so more help in that department would be very much welcome.