Malcolm Tredinnick wrote:
> Then focus your attention on that one. If
> necessary, put some debugging prints into the Django source at one of
> the points in the traceback (starting from the bottom) to see what might
> be going on. Print the information to sys.stderr, which will go to your
> Apache error log, but remember to call sys.stderr.flush() if you want to
> see the output, because mod_python unfortunately buffers stderr.
That you have to flush sys.stderr to get it to appear in the Apache
error log has nothing to do with mod_python as mod_python doesn't touch
sys.stderr, it just uses whatever is inherited from Python when it is
initialised.
What you will find is that it is Apache that substitutes the underlying
operating system provided stderr file stream with its own which directs
stuff to the Apache error log instead.
That said, if you are using mod_python and since it is likely to be a
temporary measure, one can also always use:
from mod_python import apache
apache.log_error('some message as a string')
That way you are guaranteed that it ends up in the Apache error log
immediately.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
