Barry Scott wrote:
> Russ,
>
> Do you want to keep working away at this or wait until 1.1 work
> starts?
I don't think the feature freeze will really get in the way of work on the
swig bindings. Most of the changes that need to be made are localized
bugfixes.
> Is it time to give up on the current SWIG bindings and
> start the design work that was talked about in another thread?
Do you mean the discussion about wrapping the API's in an easier to use
interface? Some of the approaches described would build on top of the
current bindings.
>
> 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.
Many callbacks are already working in the way you describe. If you let me
know which callbacks aren't working I can fix them.
>
> 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
I think all API functions do propagate errors from callbacks. Even if they
don't, exceptions still won't be lost because they are kept track of in
global data (technically thread-specific data).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 6 19:51:25 2003