Could be good to include some text about using the python loggers on that WSGI debug page, rather than relying on the apache logging mechanisms.
In django land ... there's django-devserver, django-debugtoolbar, and django-lumberjack. All of them more or less share the same profilers and such. The only differences being that devserver targets the terminal, debugtoolbar targets the in browser toolbar, and lumberjack tries to be a bit more flexible and uses python-logging. -k > > Once I have reviewed what other profiler options may exist and the > pros and cons of each, I am likely to include a section on using > profiling tools in: > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques > > So people could always go there. > > Graham > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
