Ticket #139 (new enhancement)

Opened 1 year ago

Last modified 7 months ago

logging: send all failure= arguments to twisted.python.log

Reported by: warner Assigned to:
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

01/11/10 14:23:06 changed by warner

or maybe just do this for log.err

01/11/10 18:01:45 changed by warner

  • milestone changed from 0.5.0 to 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 ?