Modify ↓
Opened 20 years ago
Closed 7 years ago
#809 closed enhancement (wontfix)
Catch stderr and output to logger
Reported by: | tonib | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | general | Version: | 0.7.1 |
Severity: | normal | Keywords: | helpwanted |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Hi,
I suggest that sys.stderr is catched and output to the logger like below
class StderrFaker: def write(self, message): message = message.strip() env.log.error(message) sys.stderr = StderrFaker()
Attachments (0)
Change History (10)
comment:1 by , 20 years ago
Milestone: | → 0.8 |
---|
comment:2 by , 20 years ago
I'm not sure this doesnt breaks the traceback in the webbrowser. Which is quite useful.
One would probably want both outputs.
comment:4 by , 20 years ago
Milestone: | 0.8 → 0.9 |
---|
I don't think this will work when using ModPython. The log-file is per project but sys.stderr is global.
I'm moving this into the future until we know if this is true.
comment:5 by , 20 years ago
Description: | modified (diff) |
---|---|
Keywords: | helpwanted added |
Priority: | normal → low |
Severity: | normal → enhancement |
So maybe implement it only in the CGI frontend?
comment:6 by , 19 years ago
Milestone: | 0.9 |
---|
comment:8 by , 18 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 1.0 |
comment:10 by , 10 years ago
Owner: | removed |
---|
comment:11 by , 7 years ago
Milestone: | unscheduled |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Not a bad idea.