[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[PATCH] Re: Multiple problems with svn python bindings

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-09-01 02:27:46 CEST

On Sat, Aug 31, 2002 at 04:20:20PM -0700, Greg Stein wrote:
> On Sat, Aug 31, 2002 at 03:46:19PM -0700, Greg Stein wrote:
> >...
> > > In other words, we just pass the PyObject through to the workaround _foo
> > > function unchanged.
> >
> > Yup, looks great. And because of the PyObject*, this would be Python
> > specific, so it goes into the swigutil_py.* files.
> Working on this now...

I've attached a patch which compiles and visual inspection seems to do the
right thing. I haven't gone thru the whole mix to try out one of these
functions -- figured on at least getting this patch out for conceptual

It introduces a swig_workarounds.h header to prototype the stubs for the
various per-language stubbing. The old STRINGLIST typemap stuff was ripped
from the .i files and use of these stubs put in place. Finally, the new
stubs were inserted into swigutil_py.c.

Since libsvn_swig_py now depends directly on the client and repos libraries,
I also tweaked build.conf to report this. There was also a small change to
add SVN_ERR_SWIG_PY_EXCEPTION_SET so that we could propagate Python errors
thru svn_error_t.


Greg Stein, http://www.lyra.org/

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Sun Sep 1 02:22:52 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.