> just to clarify, when you say python bindings, are you referring to > swig? Not really: SWIG is a *generator*: it helps building the wrapper code that stands between the Python interpreter (SWIG may generate wrapper for many other language) and the underlying C native library (.so). Python bindings are made of Python (.py) code and C wrappers (c file compiled into a .so lib), which are both generated with the SWIG tool.
> 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? SWIG is only required to *build* the bindings, not to run them. The SWIG version only matters when you build the bindings. > I have also tried removing that PYTHONPATH statement from the > trac.conf file and end up with the same result... You could try to add the path to your bindings before sys.path, not after > is that svn-python directory the correct place to have python looking > for the bindings? I guess that LD_LIBRARY_PATH also matters to locate the .so part of the bindings. > appreciate all your help... first time an issue has come up with trac/ > svn installs and first time dealing with bindings? ;) Do you really need to rebuild SVN? Is there no way to add the packages with your favorite package manager? 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 -~----------~----~----~----~------~----~------~--~---
