#9434: mod_python and unique PythonInterpreters
------------------------------------+---------------------------------------
Reporter: lifewithryan | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by grahamd):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
What probably matters is whether the virtual hosts are distinguished by
server name. If the virtual hosts are for the same server name but on
different ports, then there may be an issue. This is because mod_python
defaults to naming sub interpreter based on server name only and doesn't
use the port. Thus two virtual hosts on different ports with same server
name will shared same sub interpreter. Another mistake which can also
cause mod_python to appear to share sub interpreters across virtual hosts,
is not defining NameVirtualHost directive in Apache configuration.
So it is clear how your system is setup, provide how your virtual hosts
are configured.
--
Ticket URL: <http://code.djangoproject.com/ticket/9434#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
