On Jul 27, 9:39 pm, Greg Troxel <[email protected]> wrote:
> After looking into the most current version of mod_python, I found
> that there is little to no support for it - development seems to have
> stopped about 1 1/2 years ago.
>
> The last active developer has suggested that users move to mod_wsgi.
> Reference:
> http://code.google.com/p/modwsgi/
>
> The message can be found at:
> http://modpython.org/pipermail/mod_python/2009-July/026279.html
>
> I would appreciate comments.
>
> I am running trac on about 5 boxes, NetBSD 4 or 5, i386 or amd64, apache
> 2.2.x. Most are running mod_wsgi and perhaps one or two mod_python. My
> plan is to make them all run mod_wsgi. I suspect that mod_python leaks
> memory into apache, even the master process, but I can't quite prove
> that.
Yes, mod_python has a problem in it whereby it doesn't destroy the
interpreter properly in Apache parent process resulting in all the
memory in use by the interpreter being leaked. See:
https://issues.apache.org/jira/browse/MODPYTHON-235
In mod_wsgi, it does destroy the interpreter properly and so doesn't
suffer the same problem.
That said, the Python interpreter itself, even when destroyed, does
leak a small amount of memory depending on which version of Python you
are using.
End result is that for mod_wsgi, you still may see Apache parent
process grow in memory usage if you do a lot of restarts or graceful
restart, rather than complete stop/start.
> mod_wsgi is slightly tricky to set up in that you need to install
> a small script but once you get it working it is entirely reliable, so
> this is in my view not a worry.
Although some like that mod_python can just refer to a installed
Python module, that it does this is a PITA. This is because it is
completely contrary to the Apache resource model and as a result the
SCRIPT_NAME value which identifies where an application is mounted is
usually never correct for mod_python. As a result, applications when
using mod_python usually have to provide a way of fudging things by
telling the application manually where it is mounted.
> So I recommend that you use mod_wsgi.
> Graham presumably would have said that too, but I'm disinterested :-)
As much as I would like to see mod_python vanish, I am not that
blatant about telling people that mod_python is a stinking pile of cow
turd and that mod_wsgi is much sweeter smelling. :-)
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
