Changes between Version 103 and Version 104 of TracSubversion

Timestamp:

Feb 22, 2012, 12:57:07 PM (12 years ago)

Author:

anonymous

Comment:

—

TracSubversion

@@ -62 +62 @@
 ==== for Python 2.7
 
+For Subversion 1.7.x there also is bindings from http://alagazam.net (see Python 2.6 section above)
+
 Use the Subversion 1.7.0 bindings from !CollabNet server edition: [http://www.open.collab.net/products/subversion/getit.html CollabNet Subversion Edge 2.1.0 (for Windows 32 or 64 bit)].
 
@@ -67 +69 @@
 
 //For the 1.6.x bidings, there's no "official" release to be found for Python 2.7, but thanks to dawuid, who contributed [attachment:svn-win32-1.6.15_py_2.7.zip] (md5 `9dba3d11c4bbb91e29deb28f569e821b`). I tested them, and they seem to work great. Simply unzip in your <python27install>\Lib\site-packages folder. Note that you must have the folder containing the matching Subversion libraries in your PATH (e.g. "C:\Program Files (x86)\Subversion\bin"). 
-
-For Subversion 1.7.x there also is bindings from http://alagazam.net (see Python 2.6 above)
 
 === BSDs
@@ -307 +307 @@
  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.
 
+ Don't use 64bit version of Python. The Subversion project does not provide amd64 or ia64 setup executables, so if you want to use Subversion integration, you’ll need to either compile the bindings yourself, or use the x86 version of Python.
+
  A good way to diagnose a //DLL load failed// error is to use the [http://www.dependencywalker.com/ depends.exe] tool from the console in which you'd run python.exe, and do a `depends.exe absolute-path-to/python.exe` instead. Then, press `F7` (//Start Profiling...// - you need at least version 2.0 of depends.exe) and type `from svn import core` at the Python prompt in the new cmd window. This will try to load the bindings, but this time you'll be able to see //why// this fails, by spotting the .DLLs shown in red in the Module list, and there are really lots of options here ;-)
 
@@ -378 +380 @@
  * If you think you've found a bug in Subversion, read these 
    [http://subversion.apache.org/issue-tracker.html instructions]
-