Re: PyGtk and gtk-3.0 compatibility
- From: Tshepang Lekhonkhobe <tshepang gmail com>
- To: John Stowers <john stowers lists gmail com>
- Cc: python-hackers-list <python-hackers-list gnome org>, gtk-devel-list gnome org, pygtk <pygtk daa com au>, Murray Cumming <murrayc murrayc com>
- Subject: Re: PyGtk and gtk-3.0 compatibility
- Date: Mon, 8 Nov 2010 01:15:34 +0200
On Sun, Nov 7, 2010 at 23:24, John Stowers <john stowers lists gmail com> wrote:
>
>> > >
>> > > John
>> > >
>> > > [1] http://github.com/nzjrs/pygtk/commits/gtk-3.0
>> > > [2] http://github.com/nzjrs/pygobject/tree/gtk-3.0
>>
>> What's the status of this now? Is there every likely to be a pygtk
>> release for GTK+ 3?
>>
>
> I suspended the work during the large round of gtk+ breakage (rendering
> cleanup mainly) and have not had the time to return to it.
>
> My original goal was to do this in a backwards compatible way. With the
> recent API changes to gtk+-3.0 this is no longer possible, things like
> the expose/draw transition will be too hard to manage in PyGtk.
> GtkApplication making use of GVariant are also going to be difficult to
> wrap, minimally, the old way.
>
> That said, I did receive some negative feedback about the idea.
> PyGObject is the recommended way in future, and keeping PyGtk alive
> might actually hold the platform back. There is certainly some truth in
> that argument. In short, I am not sure what do do.
Don't bother adding 3.x support to PyGTK. Let it remain at current
released version forever, and give it only security/critical fixes. A
good migration (to PyGobject) guide should do, at least for the most
popular tasks.
--
blog: http://tshepang.tumblr.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]