[pygtk] Re: python bindings for gtk 2.4 and gnome 2.6
Christian Robottom Reis
kiko at async.com.br
Fri Mar 5 23:47:45 WST 2004
Rounding out messages I meant to answer but never did:
On Fri, Feb 20, 2004 at 04:23:41PM +0100, Erik Grinaker wrote:
> Now, I've been thinking a bit about how we should organize this, and
> have a few issues I'd like to discuss.
> - should we explicitly notify james and the rest of the guys, and get
> some of his thoughts on this? doesn't seem like he's reading the list
I've been meaning to telephone him since it's been hard to get him on
via email (though we do sense his presence <wink>). I'll do so as soon
as I find time.
> - should we start by doing a bugfix / extension release of the 2.0.x
> series, or do a release for gtk+ 2.2 / gnome 2.4, or just start working
> on a complete 2.4 / 2.6 right away?
The first release will be based on 2.2.0. We've got a small enough team
to not really be able to do many bugfix releases, and the intervals
between releases have been very large. We would like to see this change,
but it requires people stepping up and helping us plan and implement
changes and fixes.
> - should we set up a new pygtk-devel mailing list (I don't know if
> there's one already), or just use the normal pygtk list and the bugzilla
> to communicate?
The main list is fine to communicate. I've just set up a
pygtk-devel at pygtk.org alias that can be used to reach the developer
> - how do we do the development? should we submit patches against the
> current cvs, get write access (at least a couple of us) to cvs, or set
> up our own cvs tree?
Use GNOME cvs; patches should be posted to the relevant Bugzilla
reports. If a report doesn't exist for something you're working on, open
it. The developer page at http://pygtk.org/developer.html is a good
resource for people wanting to get involved in the project.
> - i'd really like to put an emphasis on documentation. I don't know how
> this is handled currently, but since pygtk will be the first contact
> many people have with gtk I think good-quality docs are very important.
> The current docs are not at all bad, but they could be improved and
> there doesn't seem to be any python-gnome documentation at all.
Note that John Finlay has added the reference and tutorial sources to
GNOME cvs too, in the module pygtk-docs. Patches are welcome, as are
bug reports (to the documentation component of the pygtk product).
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the pygtk