Apache Mod-Python - Resolved: (MODPYTHON-41) Calls to PyErr_Print should be followed by fflush().

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > April 2005 > Resolved: (MODPYTHON-41) Calls to PyErr_Print should be followed by fflush().





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Resolved: (MODPYTHON-41) Calls to PyErr_Print should be followed by fflush().
Nicolas Lehuen (JIRA)

2005-04-30, 2:45 am

[ http://issues.apache.org/jira/brows...HON-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.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com