You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by "Nicolas Lehuen (JIRA)" <ji...@apache.org> on 2005/04/30 09:15:18 UTC
[jira] Resolved: (MODPYTHON-41) Calls to PyErr_Print should be followed by fflush().
[ http://issues.apache.org/jira/browse/MODPYTHON-41?page=all ]
Nicolas Lehuen resolved MODPYTHON-41:
-------------------------------------
Assign To: Nicolas Lehuen
Resolution: Fixed
Fix Version: 3.2.0
> 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.0
>
> 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