I see that there is a task (
http://subversion.tigris.org/project_tasks.html) to provide better Python
bindings for Subversion and to provide a higher level API to make usage
easier. I know there is http://pysvn.tigris.org but it isn't implemented to
take advantage of Swig's automatic tracking of the lower level apis. That
being said, this task has two parts:
Finish the Python bindings to provide full Subversion usage
Provide a higher level API for Subversion binding usage
The first is required and will be dealt with but is there any
interest/benefit in the second? I would like to tackle these and here is my
1. I need to get the Python bindings to expose all necessary functionality
of the Subversion API.
2. Once that is complete, we would create Python classes to encapsulate the
lower level api calls making usage of the Python bindings easier.
3. Document the new api.
I know this is a simplified approach but those are the steps that will be
taken if we decide to do this and I am the person doing it. Please provide
any feedback and if you are interested in helping, please let me know.
Received on Thu Feb 8 19:46:25 2007