Re: Merging python-bindings-improvements to trunk

On 8/5/05, Blair Zajac <blair@orcaware.com> wrote:
> Do the new bindings support the same interface as the old bindings, so
> that scripts can be use unmodified?
Yes. All 1.2.x scripts should work on 1.3.x. If they don't, file a bug
report :) It's a good idea to try your 1.2.x scripts now on the
python-bindings-improvements branch, so we can be sure that everything
is compatible.

> Which Subversion release will see the new bindings? 1.3.0?
Yes.

> Is there anyway we can get them into 1.2.x as a set of versioned
> bindings so scripts don't break?
1.2.x scripts should work better than ever on 1.3.x. So I don't see a
need for versioning. :)

> Now that this work will be going into trunk soon, where will work on the
> present bindings in the 1.2.x branch be worked on? Should we have a
> separate 1.2.x-bindings branch to support work on the current bindings
> that doesn't immediately go into the 1.2.x branch?
That's a good idea.

I'd definitely like to see some of the 1.3.x fixes also go into 1.2.x
so that users of the old bindings can benefit. Do you have ideas on
which fixes would be appropriate for 1.2.x?

> BTW, I recently tried to write a Python script where I could have used
> svn_client_info(), but the callback and baton haven't been properly
> handled in SWIG, like svn_client_log(), so it's unusable. Do the new
> bindings handle svn_client_info() so this portion can be back-ported?
I haven't worked on that yet. Send me some sample code, and I'll try
to make it work.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org