On Sun, 14 Dec 2003 22:47:37 +0100
Xavier Ordoquy <[EMAIL PROTECTED]> wrote:
[snip]
> * You may not add API in the stable (2.6.x, for instance) phase. You
> must wait until the next schedule to add API. Remember, it's not a
> problem if you must wait to add API, because you must only wait <6
> months until the next stable release. For instance, GTK+ 2.4 adds API
> compared to GTK+ 2.2.
>
> <That one may not make sense at first read, but afterwards it appears to
> be ok since pygtk uses a X.X for the required function
> (pygtk.require('2.0') as for now). We may not know if the micro version
> is more or less than the required. However as we are not working on
> features developpement but on wrapper I'm mixed on that "no API
> addition">
I think this makes sense. As an example take a missing API feature I
reported recently. widget.modify_xyz could not be passed a None argument
in order to reset the xyz-attribute to the default style. So in my
application I don't use that feature. Imagine a developer who develops
an application with a later patch-level of pygtk that can do
widget.modify_xyz(None) without complaining. However, the application
would break on a slightly older pygtk installation. That would be a major
pain for the application maintainer. It would be ok, however, if the
application could require a pygtk version that is known to always
support widget.modify_xyz(None).
>
[snip]
> --
> Xavier Ordoquy <[EMAIL PROTECTED]>
> Gnome
Just my 2 cent.
Felix
------------ __\|/__ ___ ___ -------------------------
Felix ___\_e -_/___/ __\___/ __\_____ You can do anything,
K�hling (_____\�/____/ /_____/ /________) just not everything
[EMAIL PROTECTED] \___/ \___/ U at the same time.
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
