quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Dumpleton (JIRA)" <j...@apache.org>
Subject [jira] Closed: (MODPYTHON-41) Calls to PyErr_Print should be followed by fflush().
Date Sun, 05 Mar 2006 04:50:40 GMT
     [ http://issues.apache.org/jira/browse/MODPYTHON-41?page=all ]
     
Graham Dumpleton closed MODPYTHON-41:
-------------------------------------


> Calls to PyErr_Print should be followed by fflush().
> ----------------------------------------------------
>
>          Key: MODPYTHON-41
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-41
>      Project: mod_python
>         Type: Improvement
>   Components: core
>     Versions: 3.1.4
>     Reporter: Graham Dumpleton
>     Assignee: Nicolas Lehuen
>      Fix For: 3.2.7

>
> In mod_python.c there are a few places where PyErr_Print() is called. The output of this
> function is sent to stderr and not to the Apache log functions. The output does make
its
> way into the Apache error log file eventually, but not straight away due to buffering
> issues. In order to ensure the output gets the logs straight away, a call should be made
> to fflush(stderr) after calling PyErr_Print(). Ie.,
>         PyErr_Print();
>         fflush(stderr);
> This will ensure that relevant lower level Python errors appear adjacent to any error
message
> logged by mod_python to the error log file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message