I am forwarding this to the dev list, since I feel it's something they could
benefit from, and add to, since they have been working with Subversion a lot
longer than I have. Comments are inline.
> -----Original Message-----
> From: Stephen Haberman [mailto:firstname.lastname@example.org]
> Sent: Tuesday, February 25, 2003 11:24 PM
> To: email@example.com
> Subject: svn win32 python bindings
> Hi Dale,
> I've been hoping for Win32 svn python bindings for awhile to use the
> subwiki and viewcvs goodies for svn, and so finally thought I'd try
> building them today, but I'm completely out of my element.
> I've been going through the archives and found that in reference to
> issue 990, you have the python bindings compiled?
I have managed a decent compilation, yes. Runtime is another matter. There
are still a few bugs to be worked out in regards to whether or not
apr_time_t is being passed around properly.
> I wouldn't want to ask you to write up a tutorial or such as
> I know they
> can be very time consuming, but given that win32 binaries are easily
> shipped from machine to machine, would it be possible for you
> to zip up
> the dll/py/pyc files that you masterfully created and then I
> (and other
> gracious win32 svn users) could drop into place alongside a 0.18 (or
> similar) svn installation?
I can certainly send you them. That's not a problem at all. In fact, what
I'll send you is a zip file that you can just unzip into <Python Install
Directory>\Lib\site-packages. that should get you going. the only caveat
is that I linked against Python 2.2. So you'll need at least that version
in order to get running.
> I think such a thing would work, but honestly don't know the
> behind-the-scenes mechanics of the svn/win32/swig/python integration
> (e.g. if the shipped 0.18 win32 binary needs to be built with some
> special swig hooks).
The whole point of having python bindings (hopefully) is that there is no
need when scripting for the svn binaries. Basically, the integration is
like this: Swig generates c files to be compiled, which are then combined
with the svn libs into shared libraries. You then only need to make these
shared libraries (.pyd on windows) visible to Python under it's
> I'd be much appreciated as it would save me from learning things I
> should probably know anyway but have already lost too much time
> struggling with.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Feb 26 20:01:10 2003