sven 0.6

It requires pysvn which you will probably want to install system-wide[1].

Alternatively, you can use Sven with mercurial. This is highly experimental at present. Look at ./sven/hg-doctest.txt for details. Sven’s hg interface is (mostly) the same as the svn interface.

Basic usage:

from sven.backend import SvnAccess
client = SvnAccess(my_svn_server_repo_uri, my_local_checkout_dir)

client.write('path/to/a/file/to/write', "Lovely content to be versioning!")
client.write('path/to/another/file', "Aw shucks, I'll version this too..",
             msg="My commit message", kind='text/plain')

last_rev_int = client.last_changed_rev('path/to/another/file')

last_rev_int = last_rev_int - 1
from sven.exc import ResourceUnchanged
try:
    earlier_version = client.read('path/to/another/file', rev=last_rev_int)
except ResourceUnchanged, exc:
    last_rev_int = exc.last_change
    earlier_version = client.read('path/to/another/file', rev=last_rev_int)

changelog = client.log('path/to/another/file', rev=last_rev_int)

Each .write writes the content to the path on the local filesystem’s checkout and then commits it to the repository. The workflow of one-write-per-commit is by design and is not likely to change soon; if you need a different workflow, you probably ought to just be using svn clients directly, anyway.

Currently sven does not help you set up an svn client or server. It assumes you’ve already got a repository and checkout set up.

The formats returned by some of its methods (particularly .log and .ls) are totally ad-hoc right now and strange; they’ll probably be formalized sooner or later.

For more detailed usage documentation please see ./sven/doctest.txt (which can be run as a test suite by python sven/backend.py)

[1] If you start to experience Segmentation faults while using sven, especially

during .write operations, your versions of svn and pysvn are likely incompatible (e.g. svn 1.5 with pysvn compiled against your earlier svn 1.4) If this happens, you should uninstall pysvn, then compile it from source. You might want to test for this upfront by running the test suite:

python sven/backend.py

New in version 0.6:

• SvnBackend.__init__ no longer takes a ‘svnuri’ argument to the remote repository as its first positional argument; it’s not used anywhere. This is a backwards-incompatible change.

• The strange ad-hoc JSONish object returned by SvnAccess.ls had an extra / prefixed to the object’s ‘href’ erroneously; now fixed.

• Experimental implementation of the Sven API for Mercurial backends now lives in sven.hg.HgAccess; it is documented in hg-doctest.txt and has a few small differences from the SvnAccess backend. It is highly incomplete (think of it as an alpha stage) and requires mercurial to be installed. Sven does not install mercurial, just like it doesn’t install pysvn.

History: