Re: Learning the Python API - early questions

Russ,

Do you want to keep working away at this or wait until 1.1 work
starts? Is it time to give up on the current SWIG bindings and
start the design work that was talked about in another thread?

Anyway...

I have been pushing on to find out what more will need fixing to get
the current bindings working. The big issue to fix is call backs.

We need a set of C functions that match the signatures like
svn_wc_status_func_t and svn_auth_simple_prompt_func_t. That call
the python callable that is stored in the "void *baton" with
the parameters converted to Python objects.

There is also the issue of catching exceptions raised in the
Python code. I hope it is possible for all call backs to pass
back an error to stop the outer operation, status, checkout,
log etc.

At the moment an error in the python code will drop me into
Dev Studio to debug the exception. It would be nice for the
wrappers to raise python exceptions rather then enter the svn
code and hit the assert calls or fall off the end of NULL
pointers.

Barry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 5 15:56:16 2003