Emmanuel Blot wrote: >> 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. >
Not even, as the generated bindings are shipped in the Subversion source tarball. You only need SWIG when building Subversion from a source checkout, or when you want to modify the .i files. So most of the time (including in this situation) SWIG doesn't even come into the picture. IIRC, the advice from the TracSubversion page comes from a time when the generated bindings /weren't/ shipped (the 1.2.x / 1.3.x period, again IIRC). I'd suggest to the original poster to follow the steps in http://trac.edgewall.org/wiki/TracSubversion#Checklist in particular step 3. -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
