On Thu, Jul 15, 2010 at 12:06 PM, Cooke, Mark <mark.co...@siemens.com>wrote:
> > > > On Sat, Jul 10, 2010 at 2:12 AM, Hugh Jennings > > <hughj...@gmail.com> wrote: > > > > Hi, > > > > I hope someone can help me. > > > > (snip) > > > > When I go to do anything that is associated with a > > repository I get an > > error saying no module named svn. > > (snip) > > > > C:\Users\generic>python > > Python 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC > > v.1500 32 bit > > (Intel)] on > > win32 > > Type "help", "copyright", "credits" or "license" for > > more information. > > >>> import svn > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > ImportError: No module named svn > > >>> > > > > I would appreciate any ideas as to what I can try next. > > > > Regards, > > > > Hugh > > > > -----Original Message----- > > From: trac-users@googlegroups.com > > [mailto:trac-us...@googlegroups.com] On Behalf Of Itamar O > > Sent: 15 July 2010 09:29 > > To: trac-users@googlegroups.com > > Subject: Re: [Trac] Python Binding problems with Trac 0.12 > > > > Hi, > > > > You need to install python-svn bindings. > > I don't think CollabNet distribute those, > > but they are available from another source of Subversion > > binaries for windows: > > http://alagazam.net/ > > > > Itamar. > > > Hi Itamar, > > Those "bindings" are just a load of files in a zip file and I am not > certain what I need to do to "install" them, can you help? > > Is it just a case of copying them to <somewhere> in my python install > tree (e.g. C:\Python26\Lib\site-packages\...)? Or is there more work > involved? > > Looking at the contents of the zip file, there are fewer files than I > already have from a previous install (from tigris when they were > packaged in an installer) although the differences seem to be mostly the > compiled python files but also a few DLLs look to be missing (such as > libaprutil-1.dll and libapriconv-1.dll) and the ones that are provided > have different names... > > Thanks, > > ~ mark c > > It has been a while since I've done that. If I remember correctly, you should simply copy the svn and libsvn directories to the site-packages directory under Python2X\Lib. The *.pyc files you might see there are the compiled files. You should remove them if you are updating. The README in the Alagazam package also states that for Py2.5+ you should rename the *.dll under libsvn to *.pyd manually. If you use the Alagazam installer to install Subversion itself, the libapr* DLLs are located under the Subversion\bin directory, so there's no need to put duplicates in the Python site-packages. Hope this help, Itamar. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
