just to clarify, when you say python bindings, are you referring to swig? there is a swig executable in /usr/local/bin (same place as svn executables) that returns version 1.3.25 which is what I built... or are there shard object libraries in use for the bindings?
I have also tried removing that PYTHONPATH statement from the trac.conf file and end up with the same result... is that svn-python directory the correct place to have python looking for the bindings? or should it possibly be up one directory to where all the libsvn_xxx.so files are? or perhaps down one directory to where the libsvn or svn directories are? appreciate all your help... first time an issue has come up with trac/ svn installs and first time dealing with bindings? ;) Steve On May 10, 9:25 am, Emmanuel Blot <[email protected]> wrote: > > PYTHONPATH includes (I believe via PythonPath "sys.path + ['/usr/ > > local/lib/svn-python'] in httpd.conf) /usr/local/lib/svn-python > > directory... there are subdirs libsvn and svn under there... > > If sys.path points to one the previously installed SVN python > bindings, then your own built bindings will never be loaded. > > Cheers, > Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
