I've got the Python SWIG bindings working now (thanks gstein for
revision 5020!) However, I had to do a little dance at the end,
because the bindings were installed by default in
/usr/local/lib/svn-python/svn/, a place where Python doesn't look.
After moving them to /usr/local/lib/python2.2/site-packages/svn/,
everything worked fine:
$ ./autogen.sh
$ ./configure --enable-maintainer-mode
$ make
# make install
$ make swig-py
# make install-swig-py
[see svn<-->python bindings install in /usr/local/lib/svn-python/svn/]
$ cd tools/cvs2svn.py
$ ./cvs2svn.py
Traceback (most recent call last):
File "./cvs2svn.py", line 17, in ?
from svn import fs, util, delta, repos
ImportError: No module named svn
# mv /usr/local/lib/svn-python/svn /usr/local/lib/python2.2/site-packages
$ ./cvs2svn.py
USAGE: cvs2svn.py [-n] [-v] [-s svn-repos-path] [-p pass] cvs-repos-path
-n dry run. parse CVS repos, but do not construct SVN repos.
-v verbose.
-s PATH path for SVN repos.
-p NUM start at pass NUM of 4.
--create create a new SVN repository
--trunk=PATH path for trunk (default: /trunk)
--branches=PATH path for branches (default: /branches)
--tags=PATH path for tags (default: /tags)
$
What's the right solution here? Should the bindings be installed in
/usr/local/lib/pythonX.Y/site-packages/, or should Python somehow be
told to look in /usr/local0/lib/svn-python/ for modules to import? Or
is there a third answer?
Greg, I think this may have been the problem you were anticipating
when we talked on the phone; if so, you were right, it bit me :-).
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 24 23:10:39 2003