Changes between Version 22 and Version 23 of TracSubversion

Timestamp:

Sep 11, 2006, 8:24:57 PM (18 years ago)

Author:

Christian Boos

Comment:

#2611 still present for Subversion 1.4.

TracSubversion

@@ -101 +101 @@
 when compiled using the pre-generated bindings that were produced using SWIG 1.3.25[[br]]
 So it seems the patch discussed above was not enough to solve the problem.
-Also, ''the issue is most certainly related to the use of multiple python sub-interpreters'', either because those are created by default when different virtual hosts are used (#2965, #3455) or because different `"PythonInterpreter"` directives are used in different <Location> sections (#2713). A workaround consists of forcing the use of a single Python interpreter, using the `"PythonInterpreter"` directive with the same argument for all the virtual hosts, as explained [comment:ticket:3455:5 here].
+Also, ''the issue is most certainly related to the use of multiple python sub-interpreters'', either because those are created by default when different virtual hosts are used (#2965, #3455) or because different `"PythonInterpreter"` directives are used in different <Location> sections (#2713). '''A workaround consists to force the use of a single Python interpreter''', using the `"PythonInterpreter"` directive with the same argument for all the virtual hosts, as explained [comment:ticket:3455:5 here].
 
 ==== Trac and Subversion 1.3.2 ====
@@ -119 +119 @@
 
 Same remark as above concerning #2611, if I have some time, I'll try to reproduce the issue.
+Update: according to comment:ticket:2965:14, the problem is still there for 1.4.
 
 See also: [http://svn.collab.net/repos/svn/tags/1.4.0-rc5/CHANGES release notes for 1.4.0]