2008/8/31 Graham Dumpleton <[EMAIL PROTECTED]>: > Yes the stdout/stderr in mod_wsgi could be made more friendly to such > code, which would help with closed check on stderr, and this is what > following issue is for: > > http://code.google.com/p/modwsgi/issues/detail?id=82 > > Even so, WSGI applications should not use stdout if they want to claim > portability and I'd also look at code that writes to stderr which > flushed stdout with some suspicion.
For mod_wsgi 3.0 have now added closed and isatty attributes to Log object as well as close() method. For wsgi.errors these aren't required, but log object also used for stderr and stdout (when enabled) and code may assume these methods may exist for stderr and stdout. The closed and isatty attributes always yield false and close() will raise a run time error indicating that log cannot be closed. Will consider back porting this to older versions if necessary. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
