After the desktopcouch.records split in bug #510159, using desktopcouch from a Python program will start with "from desktopcouch.records import CouchDatabase". There should be also a very similar interface to directly access Ubuntu One CouchDBs.
Entry point: "from desktopcouch.ubuntuone import CouchDatabase"
desktopcouch.ubuntuone.CouchDatabase should be a subclass of desktopcouch.records.CouchDatabase. It should attempt to retrieve an Ubuntu One access token from the keyring and use it for access. If no token, or no keyring, is available, then throw an error. It must be possible to pass a valid oauth token to the d.u1.CouchDatabase constructor (for use in server/webapp environments). (NB: this is already possible with the oauth_tokens parameter to CouchDatabase; this needs to be documented).
Note that there is a bug in desktopcouch.records overescaping slashes in URLs, so a request for contacts/_design/get_records_and_type really tries to access contacts%2F_design%2Fget_records_and_type. This works in desktopcouch because DC recognises the wrongness and issues a 302 redirect to the right URL; in Ubuntu One Couch it throws a 401, not a redirect.
Note that desktopcouch.