[pygtk] Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

[Tim Janik]

On Thu, 21 Jun 2007, Elijah Newren wrote:

> Just realized that pygtk and gtk-devel-list subscribers may not be on
> d-d-l.  So I'm forwarding this.  See
> http://mail.gnome.org/archives/desktop-devel-list/2007-June/msg00109.html
> for the thread and discussion.  Please jump in.
>
> ---------- Forwarded message ----------
> From: Elijah Newren <newren at gmail.com>
> Date: Jun 21, 2007 8:05 PM
> Subject: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME
> 2.19.4 released yet?)
> To: Gnome Desktop Development List <desktop-devel-list at gnome.org>
>
>
> Hi,
>
> As noted in bug http://bugzilla.gnome.org/show_bug.cgi?id=449318,
> there was a recent gtk+ API change.  jdahlin just barely told me that
> the changed API has existed since 1998, long before gtk+-2.11.x (and
> pointed me to http://bugzilla.gnome.org/show_bug.cgi?id=447214).  This
> API change breaks pygtk and means that much of GNOME cannot be
> compiled.  But it doesn't seem clear who should fix this.  Should gtk+
> revert it or somehow fix the API break, or is this an API break we
> want and expect pygtk to adapt to?

so far, my take on the issue is that PyGtk should adapt to that
change by not using tooltips->tips_data_list, because:
a) i haven't seen a single argument yet about why giving up using
    tips_data_list would be bad for PyGtk or any other application
    for that matter;
b) GtkTooltips is going to be deprecated in 2.12 anyways, so there
    is little use in continuing to use it anyway.
c) note that the actual compilation changes could easily be ironed out
    by Gtk+ by doing s/_tips_data_list/tips_data_list/ but was introduced
    deliberately, to catch remaining tips_data_list uses in third-party
    code which should be removed now, since tips_data_list became a
    mere alias for NULL for future Gtk+ versions.

> Elijah

---
ciaoTJ