2009/8/13 gert <[email protected]>: > > On Aug 12, 10:50 pm, Graham Dumpleton <[email protected]> > wrote: >> 2009/8/13 gert <[email protected]>: >> >> >> > On Aug 12, 5:40 pm, gert <[email protected]> wrote: >> >> On Aug 12, 7:41 am, Graham Dumpleton <[email protected]> >> >> wrote: >> >> >> > I believe I have finally fixed the UTF8/UCS2 issue for WSGI script >> >> > paths on Window, so am close to a final release candidate. This issue >> >> > was where unicode characters could be used in file system directories >> >> > holding WSGI script file, or in name of WSGI script file itself. >> >> >> > The only remaining thing I am looking at is the UTF8/UCS2 issue as it >> >> > relates to WSGIPy3kWarningFlag and WSGIPythonHome directives on >> >> > Windows. Once I get my head around and do any further changes, will >> >> > create a tar ball for another release candidate. >> >> >> > For the adventurous out there who are using the subversion trunk, >> >> > please consider an update and provide feedback if any problems seen. >> >> > Pay particular attention to whether logging via sys.stdout, sys.stderr >> >> > and wsgi.errors is working correctly, as had to make some tweaks to >> >> > that code. >> >> >> > Let the countdown for gert screaming about problems begin. ;-) >> >> >> I did not test it yet, But I am defenatly going to scream if think >> >> WSGIPy3kWarningFlag is what I think it is.... >> >> > Goddammit i knew it >> >> > r...@localhost:~/mod_wsgi# make >> > /usr/httpd/bin/apxs -c -I/usr/include/python3.1 -DNDEBUG mod_wsgi.c >> > -L/usr/lib -L/usr/lib/python3.1/config -lpython3.1 -lpthread -ldl - >> > lutil -lm >> > /usr/httpd/build/libtool --silent --mode=compile gcc -prefer-pic -O2 - >> > DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/httpd/include -I/ >> > usr/httpd/include -I/usr/httpd/include -I/usr/include/python3.1 - >> > DNDEBUG -c -o mod_wsgi.lo mod_wsgi.c && touch mod_wsgi.slo >> > mod_wsgi.c:138:2: error: #error Sorry, there is no WSGI specification >> > for Python 3.X as yet. >> > apxs:Error: Command failed with rc=65536 >> > . >> > make: *** [mod_wsgi.la] Error 1 >> >> Run: >> >> ./configure --help >> >> I am sure you will work it out. >> >> The WSGIPy3kWarningFlag is not related to this. Read the change files >> on the wiki. >> >> I will be moving the Python 3.0 stuff out of changes file into >> separate document as will not be advertising it as part of release. > > I like this one > WSGILazyInitialization On > And this one > WSGIRestrictEmbedded On
The latter has been in there since mod_wsgi 2.0. > I wonder why you would not make the first one default? not able to > share data is a security bonus not a drawback. Its the other way > around it would make it a drawback. Also if this would solve the main > python memory leak on restart who the hell is going to turn this off ? People will care because the memory usage requirements of each separate process is greater. Count up all the processes you may be running and it may push you over your memory limitations on small memory hosting plan. But yes, if running worker MPM and single daemon mode process, then it may help to reduce memory usage. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
