https://github.com/jelmer/subvertpy
Alternative Python bindings for Subversion
https://github.com/jelmer/subvertpy
python python-bindings subversion
Last synced: 6 months ago
JSON representation
Alternative Python bindings for Subversion
- Host: GitHub
- URL: https://github.com/jelmer/subvertpy
- Owner: jelmer
- License: lgpl-2.1
- Created: 2012-04-02T23:46:58.000Z (almost 14 years ago)
- Default Branch: master
- Last Pushed: 2025-01-21T12:37:09.000Z (about 1 year ago)
- Last Synced: 2025-01-21T13:38:05.933Z (about 1 year ago)
- Topics: python, python-bindings, subversion
- Language: C
- Homepage: https://jelmer.uk/code/subvertpy
- Size: 34.8 MB
- Stars: 16
- Watchers: 4
- Forks: 14
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- Changelog: NEWS
- License: COPYING
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
- Authors: AUTHORS
Awesome Lists containing this project
README
Subvertpy
=========
Homepage: https://github.com/jelmer/subvertpy/
Python bindings for the Subversion version control system that are aimed to be
complete, fast and feel native to Python programmers.
Bindings are provided for the working copy, client, delta, remote access and
repository APIs. A hookable server side implementation of the custom Subversion
protocol (svn_ra) is also provided.
Differences with similar packages
---------------------------------
subvertpy covers more of the APIs than python-svn. It provides a more
"Pythonic" API than python-subversion, which wraps the Subversion C API pretty
much directly. Neither provide a hookable server-side.
Dependencies
------------
Subvertpy depends on Python 3.8, and Subversion 1.14 or later. It should
work on Windows as well as most POSIX-based platforms (including Linux, BSDs
and Mac OS X).
See https://subversion.apache.org/ for instructions on installing Subversion.
Installation
------------
Standard distutils are used - use "setup.py build" to build and "setup.install"
to install. On most platforms, setup will find the Python and Subversion
development libraries by itself.
Development
-----------
If using GCC it might be useful to disable the deprecation warnings when
compiling to see if there are any more serious warnings:
make CFLAGS="-Wno-deprecated-declarations"