Re: Merging python-bindings-improvements to trunk

kfogel@collab.net wrote:
> David James <james82@gmail.com> writes:
>
>>I'd like to merge my changes from the python-bindings-improvements
>>branch to trunk. Please take a look and let me know what you think!

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?

A bunch of questions on the new bindings (just kinda a brain dump :) )

Do the new bindings support the same interface as the old bindings, so
that scripts can be use unmodified?

Which Subversion release will see the new bindings? 1.3.0?

Is there anyway we can get them into 1.2.x as a set of versioned
bindings so scripts don't break? Can we version the bindings so that we
can keep the current bindings and have scripts move up when they want
to? Something like

from svn2 import core, client, repos

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?

Regards,
Blair

-- 
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion and Orca training and consulting
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org