Thanks for this patch.  I have applied it and added support for keyword
arguments to a lot of the functions in the gtk.override file.  I was able
to run the examples/ide/browse.py example almost without modification
(just adding `import ltihooks' to the top, as I was running it from the
build directory, and changing the name of one variable), and it subclasses
GtkObjects and uses keyword arguments.

I think I have sorted out all the bugs related to the wrapper rescue code
in the destructor, but I am not that happy with the code (according to the
change log it is evil :).  It would be nice if python provided a more
general way of doing this sort of thing.

I will put out another snapshot tarball when I have a few more things
working.

BTW, I switched the stable version of pygtk and gnome-python over to using
the cvs automake, so now you can use an (almost) standard version of
automake to build gnome-python from cvs.

James.

--
Email: [EMAIL PROTECTED]
WWW:   http://www.daa.com.au/~james/


On Fri, 31 Mar 2000, Toby D. Reeves wrote:

> James,
> 
> The ExtensionClass based pygtk looks great so far.  I've been watching CVS
> as you built it up and have been waiting for you to announce that it is
> ready for folks to look at it.
> 
> I've attached a CVS diff that make the generated code use
> PyArg_ParseTupleAndKeywords instead of PyArg_ParseTuple.  This allows
> keywords to be used  to override default arguments, like in the old pygtk.
> My implemention is kind-of brute force.  It could be changed to only use
> ParseTupleAndKeywords for functions and methods that have been assigned
> default argument values.
> 
> The GtkItemFactory code in both the old and new pygtk has a refcount
> problem.  The attached python code demonstrates the bug.  I have looked at
> the gtk+ code and do not see a simple fix.   Maybe someone else will.
> Basically, gtk_item_factory_create_item()  does not allow a GtkDestroyNotify
> to be specified for the callback_data.
> 
> I look forward to using the added capabilities of the new pygtk in a
> reorg/rewrite of our hyperspectral code.
> 
> I'm glad that you agreed that using ExtensionClass was a good idea.
> 
> Later,
> 
> Toby
> 

-
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]

Reply via email to