Is it possible for you to provide meaningful responses? A simple, yes I see a logged exception when I have a syntax error in WSGI script file would suffice. Better still if you actually post the section of log file showing the exception. That it compiles doesn't mean much.
Graham 2009/8/25 gert <[email protected]>: > > On Aug 24, 1:00 pm, Graham Dumpleton <[email protected]> > wrote: >> 2009/8/18 Graham Dumpleton <[email protected]>: >> >> >> >> > 2009/8/18 Graham Dumpleton <[email protected]>: >> >> 2009/8/16 gert <[email protected]>: >> >> >>> this does not show any error messages in apache log ? >> >> >>> [Sun Aug 16 14:57:12 2009] [info] [client 192.168.2.17] mod_wsgi >> >>> (pid=5791, process='www', application=''): Loading WSGI script '/usr/ >> >>> httpd/www/appwsgi/wsgi/upload2.wsgi'. >> >> >>> import os,sys >> >>> def application(environ, response): >> >>> #query=environ.get['QUERY_STRING'] >> >>> query=os.path.join(os.path.dirname(__file__),'teeeeeeeeeemp') >> >>> print('query=',query,file=sys.stderr) >> >>> range=environ.get('HTTP_RANGE','bytes=0-').replace >> >>> ('bytes=','').split(',') >> >>> offset=[] >> >>> for r in range: offset.append(r.split('-')) >> >>> with open(query,'wb') as f >> >> >> You are missing a ':' on end of preceding line. >> >> > FWIW, the underlying problem is possibly a bug in Python 3.X. Am still >> > trying to verify this. >> >> > The Python parsing routine is returning NULL indicating it failed to >> > parse the code, but doesn't appear to have set the Python exception >> > state as it should. This behaviour is different to Python 2.X. >> >> > For now, I have added an extra message in error logs indicating a >> > parsing error, but no details of what the parsing error will be >> > logged. >> >> Gert, fixed. Try trunk again. >> > > rm -rf .libs > rm -f mod_wsgi.o mod_wsgi.la mod_wsgi.lo mod_wsgi.slo mod_wsgi.loT > rm -f config.log config.status > rm -rf autom4te.cache > checking Apache version... 2.2.11 > configure: creating ./config.status > config.status: creating Makefile > /usr/httpd/bin/apxs -c -I/usr/include/python3.1 -DNDEBUG - > DMOD_WSGI_ENABLE_PY3K 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 -DMOD_WSGI_ENABLE_PY3K -c -o mod_wsgi.lo mod_wsgi.c && touch > mod_wsgi.slo > In file included from /usr/include/python3.1/Python.h:8, > from mod_wsgi.c:127: > /usr/include/python3.1/pyconfig.h:1075:1: warning: "_POSIX_C_SOURCE" > redefined > In file included from /usr/include/sys/types.h:27, > from /usr/httpd/include/apr.h:127, > from /usr/httpd/include/ap_config.h:25, > from /usr/httpd/include/httpd.h:43, > from mod_wsgi.c:34: > /usr/include/features.h:158:1: warning: this is the location of the > previous definition > In file included from /usr/include/python3.1/Python.h:8, > from mod_wsgi.c:127: > /usr/include/python3.1/pyconfig.h:1094:1: warning: "_XOPEN_SOURCE" > redefined > In file included from /usr/include/sys/types.h:27, > from /usr/httpd/include/apr.h:127, > from /usr/httpd/include/ap_config.h:25, > from /usr/httpd/include/httpd.h:43, > from mod_wsgi.c:34: > /usr/include/features.h:160:1: warning: this is the location of the > previous definition > /usr/httpd/build/libtool --silent --mode=link gcc -o mod_wsgi.la - > rpath /usr/httpd/modules -module -avoid-version mod_wsgi.lo -L/usr/ > lib -L/usr/lib/python3.1/config -lpython3.1 -lpthread -ldl -lutil -lm > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
