On 5/2/06, Blair Zajac <blair@orcaware.com> wrote:
> David James wrote:
> > On 5/2/06, Walter Mundt <emage@spamcop.net> wrote:
> >> Are there any issues with the Python bindings that will need fixing
> >> other than the one linked on the ideas page? (I would consider any
> >> other instance of the can't-assign-to-a-function-pointer problem part of
> >> that issue, so what I'm asking for is any known problems _not_ stemming
> >> from that.)
> > For sure! The link on the issues page is just an example. I don't
> > think that 'single example' is representative at all of what needs to
> > be done.
> >
> > What I'd really like to see is a general clean up of the Python
> > bindings to have a more usable class structure, similar to the Ruby
> > bindings. It'd be great if you could just type:
>
> How does this proposed work relate to the pysvn project:
>
> http://pysvn.tigris.org/
>
> It looks like there already exists a Pythonic svn interface.
>
> Does that provide many of the features already discussed here?
PySVN does offer a simple (and documented!) interface to much of the
Subversion command-line client functionality, but it doesn't provide
extensive coverage of Subversion's APIs. Further, PySVN doesn't
integrate with our Python bindings at all, but instead bypasses them
and interacts directly with the C API.
On the other hand, the Subversion Python bindings *do* have pretty
comprehensive coverage, but very little of the available functionality
is documented or easy to use. For a summer of code project, I'd like
to see us make our Python bindings be as easy to use as PySVN or our
very own Ruby bindings.
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
Received on Tue May 2 23:17:41 2006