On Sunday, January 9, 2011, octopusgrabbus <[email protected]> wrote:
> I would like to see more from Django on what it chooses to,
> specifically around the loading or not loading of pages. I am running
> Django on RHEL 5 WS, with mod_python. I want to stick with mod_python,
> despite the testimonies its replacement is better.

Slightly off topic, but:

"Better" isn't the issue. Mod_python has been deprecated by it's
authors. It is, for all practical intents and purposes, a dead
project. If you have a RHEL support contract, Redhat will continue to
provide support, but I'd be surprised if that support extended much
beyond critical security updates. If you are starting a new project,
you would be well advised to look at mod_wsgi, or another deployment
option.

> Are there switches I can set to get more granular (detailed) logging
> in Django, or will I have to tweak Apache's configuration to log more?

it's not entirely clear to me what it is you want to see logged.
Django's decision to load or not load a page is essentially just "just
the Regex pattern match", and success is logged as a page load in your
web server access log.

The version of Django currently in development (soon to be 1.3) has
some additional logging, but doesn't give any particular insight into
the URL loading process. Django Debug Toolbar can also give some
visibility to internals.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django 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/django-users?hl=en.

Reply via email to