On Fri, 2005-04-08 at 16:11 +0200, Murray Cumming wrote: > On Fri, 2005-04-08 at 15:29 +0200, Murray Cumming wrote: > > Is it normal to change the .defs (which should > > describe the C API) to get a different python API? > > On irc, Johan Dahlin also said: > > murrayc> Is there really no way to add API without changing .defs? > jdahlin> murrayc: there is, let me see > jdahlin> murrayc: in foo.override, do % \n define class.method > jdahlin> murrayc: and then _wrap_klass_with_underscore_method_name > > I would prefer that, so that > - The .defs are just a description of the C API. > - We can regenerate the .defs without worrying about redoing our > changes/hacks.
Filip, I have added your get_key() method in the .override file, without changing the .defs. I'm not sure if this works. I have not tried it in an example, because I am not sure where this should be used anyway. Maybe you could add an example for it? -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
