Opened 15 years ago
Last modified 14 years ago
#139 new enhancement
logging: send all failure= arguments to twisted.python.log
| Reported by: | Brian Warner | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | logging | Version: | 0.4.1 |
| Keywords: | Cc: |
Description
I think it would be best to have foolscap.logging.log.msg tell twisted.python.log about any failure= arguments it sees. This would make foolscap's log.err behave better w.r.t. unit tests.
Change History (2)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
| Milestone: | 0.5.0 → eventually |
|---|
or maybe leave this up to an application-level wrapper, like how we do it in tahoe (allmydata.util.log.err). I guess the question is, when would it *not* be appropriate for a failure sent to foolscap.logging.log.err to also get sent to twisted.python.log.err ?
Note: See
TracTickets for help on using
tickets.
or maybe just do this for
log.err