#3455: Retrieving a changeset results in an empty page
---------------------+------------------------------------------------------
Reporter: cboos | Owner: jonas
Type: defect | Status: closed
Priority: normal | Milestone:
Component: general | Version: devel
Severity: major | Resolution: worksforme
Keywords: |
---------------------+------------------------------------------------------
Changes (by cboos):
* status: new => closed
* resolution: => worksforme
Comment:
Great! So without the `"PythonInterpreter"` directive, mod_python was
using ''different'' interpreters for different virtual hosts by default; I
didn't know that, but it's true that it's well documented, e.g. from
[http://www.modpython.org/live/mod_python-3.2.8/doc-html/pyapi-
interps.html Mod_python Manual 4.1]:
Default behaviour is to name interpreters using the Apache virtual server
name (!ServerName directive). This means that all scripts in the same
virtual server execute in the same subinterpreter, but scripts in
different virtual servers execute in different subinterpreters with
completely separate namespaces.
This is a bit unfortunate for us, as it's apparently a well-known source
of problems with extensions: see
[http://www.python.org/doc/current/api/initialization.html#l2h-779
Py_NewInterpreter], look for '''Bugs and caveats'''.
So that solution might also cure the #2611 issue... have you tried? (I'm
asking because you said you were able to reproduce that issue while using
the 1.3.2 bindings)
--
Ticket URL: <http://trac.edgewall.org/ticket/3455#comment:6>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
