On Wed, Sep 10, 2003 at 15:14 -0500, Ben Collins-Sussman wrote:
> Barry Scott <nospam@barrys-emacs.org> writes:
>
> > 3. Can you build tools on top of its API's? Answer today: No. We
> > need docs of the python API to SVN and we need examples.
>
> The python API is the same as the C API. And the C API is fully
> documented in all the public header files. And there are all sorts of
> example programs in the source tree, both in C and python. And
> there's even a whole chapter in the book about using the C API, and a
> couple O'Reilly articles about that on our 'links' webpage too. I'm
> not sure what more you might want.
I have had several problems in understanding the python API in the past,
nothing that could have found in the C api docs as it pertains to how
things translate from C to python. For example in the open method in:
http://codespeak.net/svn/vpath/trunk/dist/vpath/subversion.py
This is in line 331 you see that real code to open a file stream to
rerieve the contents of a versioned resource is commented out and hacked
around with opening a pipe to svn cat. I would be really interesting in
implementing that without the pipe by using the avn api directly. Do you
have any clues how to make that work?
BTW:
The vpath module abstracts operations on path names for local filesystem
and subversion URLs. It has two subversion implementations, one using
pipes to the svn command line and one using the subversion python API.
The one through the API is not complete as I was unable to implement
opening streams properly as well as finding examples for getting a log
editor to work.
--
Jens-Uwe Mager <pgp-mailto:F476EBC2>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 10 23:04:10 2003