Yeah, I copied the files and renamed them so I have both the .dll and .pyd
files in the directory.  I also rebooted the server, though I'm not sure why
that would matter.  Still no luck :(
____________________________________
Brian Ellis

On Thu, Feb 17, 2011 at 1:11 AM, Cooke, Mark <mark.co...@siemens.com> wrote:

> >       > From: Brian Ellis [mailto:bel...@ticketbiscuit.com]
> >       > Sent: Wednesday, 16 February, 2011 3:40 AM
> >       > To: users@subversion.apache.org
> >       > Subject: Python SVN Bindings on Windows Server 2008 x64
> >       >
> >       > Hi, sorry if this has been covered before but I'm new to
> >       > Subversion admin and can't really find a clear answer.  My
> >       > goal is to use the python scripts in subversion\tools,
> >       > specifically validate-extensions.py in this case.  I am
> >       > running VisualSVN Server 2.15, built on Subversion 1.6.15 and
> >       > have 32-bit Python 2.7.1 set up on the machine at the moment.
> >       >
> >       > When I set up the hook, I got an error that the svn module
> >       > could not be found.  I installed the latest libsvn bindings I
> >       > could find
> >       > (http://trac.edgewall.org/attachment/wiki/TracSubversion/svn-w
> >       in32-1.6.15_py_2.7.zip
> > <http://trac.edgewall.org/attachment/wiki/TracSubversion/svn-w
> > %0Ain32-1.6.15_py_2.7.zip>  from
> >       http://trac.edgewall.org/wiki/TracSubversion) > but I
> > still can't load
> >       the svn module.  If I run 'from svn
> >       > import repos' from the command line, I get:
> >       >
> >       > File "C:\Python27\lib\site-packages\libsvn\core.py", line 21,
> >       > in swig_import_helper
> >       > _mod = imp.load_module('_core', fp, pathname, description)
> >       > ImportError: DLL load failed: The specified procedure could
> >       > not be found.
> >       >
> >       >
> >       > Am I missing something?  I also tried the Python27 64-bit
> >       > release but precompiled svn bindings don't appear to be
> >       > available for it and I would prefer not to go through
> >       > everything required to build them myself.
> >       >
> >       > Thank you in advance for your help.
> >       >
> >       > Brian Ellis
> >       >
> >       > -----Original Message-----
> >       > From: Joel Low [mailto:j...@joelsplace.sg]
> >       > Sent: 16 February 2011 00:11
> >       > To: Brian Ellis
> >       > Cc: users@subversion.apache.org
> >       > Subject: RE: Python SVN Bindings on Windows Server 2008 x64
> >       >
> >       > [JL] Hi Brian, you can try to check if the SVN DLLs are
> >       > accessible from your 32-bit Python (so 32-bit SVN DLLs,
> >       > Program Files (x86) folder, etc), perhaps by ensuring that
> >       > the Subversion bin directory is in PATH. Remember that hook
> >       > scripts are run without environment variables defined so you
> >       > may have to redefine PATH in your hook script.
> >       >
> > On Wed, Feb 16, 2011 at 3:55 AM, Cooke, Mark
> > <mark.co...@siemens.com> wrote:
> >
> >       Hi Brian,
> >
> >       Here are some notes I made for myself about upgrading
> > the bindings when
> >       I upgrade Trac:
> >
> >       ~ deleted the old svn and libsvn directories from
> >       C:\Python26\Lib\site-packages
> >
> >       ~ opened the python bindings .zip and copied the two directories
> >        to site-packages
> >
> >       ~ copied all libsvn\_*.dll files to _*.pyd [1]
> >
> >       ~ restarted the server and crossed fingers...
> >
> >       [1] I found this recommended in the t.e.o wiki at
> > TracSubversion...
> >          http://trac.edgewall.org/wiki/TracSubversion#forPython2.6
> >
> >       ...in particular have you copied/renamed the .dll
> > files?  Hope this
> >       helps...
> >
> >       ~ Mark C
> >
> > -----Original Message-----
> > From: Brian Ellis [mailto:bel...@ticketbiscuit.com]
> > Sent: 16 February 2011 23:26
> > To: Cooke, Mark
> > Cc: Joel Low; users@subversion.apache.org
> > Subject: Re: Python SVN Bindings on Windows Server 2008 x64
> >
> > In case it helps, I loaded up the 32-bit depends.exe as
> > recommended in the TracSubversion FAQ and tried the load the
> > core module from there ('from svn import core').  I receive the error:
> >
> > LoadLibraryExA("C:\Python27\Lib\site-packages\libsvn\_core.pyd
> > ", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned NULL.
> > Error: The specified procedure could not be found (127).
> >
> > _core.pyd is located at that path so I'm not sure why it
> > can't find it.
> > ____________________________________
> > Brian Ellis
> >
> I'm clutching at straws here but did you rename the files or copy/rename
> them?  I.e. do you just .pyd or both .pyd and .dll?  If the former, try
> copying back to .dll as well (this is what I have).  You will need to
> bounce apache (if you are using it)...  The information I could find
> when I was looking into this was somewhat confused but I seem to
> remember I had very similar problems with only one or the other that
> were fixed when I kept both.
>
> Just checking the Trac site again
> (http://trac.edgewall.org/wiki/TracSubversion#checklist-windows) I
> remember reading this before:
>
>  According to the README.txt file for the Subversion bindings, if you
> are using Python 2.5+ you need to rename all the .dll files in the
> libsvn folder to .pyd files. Upon further research,
> http://www.python.org/doc/faq/windows/#is-a-pyd-file-the-same-as-a-dll
> indicates you may need to have both the .pyd and .dll version of the
> libsvn files available. This resolved both the 'ImportError: No module
> named _core' error (with only the DLL) and the 'ImportError: DLL load
> failed' (with only the pyd) when testing from the console, and the
> browser.
>
> ...I hope this fixes it!
>
> ~ mark c
>

Reply via email to