Re: Python bindings

Lele Gaifax wrote:

> What I'm stating is that Perl and Python are different enough to
> warrant a different implementation of the bindings. I still think
> that the benefit of using swig with Python is very debatable, while I
> know that it's a must for practical reasons in the Perl world.

I think you are mistaken about that; it would be just as practical to create a
Perl XS interface directly with Subversion. But as I think Ben already
asserted, we would lose the shared knowledge gained by writing both Perl and
Python interfaces to the common SWIG framework. Additionally, any of the other
languages which work with SWIG (Ruby, Tcl/TK, OCAML, and C#) could be used in
the future for Subversion, with far less effort than creating direct API's.

Pyrex only helps Python and only those people who share your view of how the API
should be structured. You could just as easily use the existing Python/SWIG
bindings with an additional layer of abstraction that fit your needs (much like
svk is doing with the Perl bindings).

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org