Opened 16 years ago
Closed 10 years ago
#125 closed defect (fixed)
foolscap.call.CopiedFailure.printTraceback wants log.logerr, but it doesn't exist. — at Version 3
Reported by: | ivank | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.8.0 |
Component: | logging | Version: | 0.5.1 |
Keywords: | Cc: |
Description (last modified by )
The offending line is if file is None: file = log.logerr
I don't think logerr
exists.
Change History (4)
comment:1 Changed 16 years ago by
Changed 14 years ago by
Attachment: | foolscap_misc_fixes.diff added |
---|
Fixes for both the log.logerr bug and a deprecation warning in banana.py
comment:2 Changed 14 years ago by
Version: | 0.3.0 → 0.5.1 |
---|
I just attached a file fixing this problem and fixing a deprecation warning in foolscap/banana.py. The file is in "hg export" format.
comment:3 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Milestone: | undecided → 0.8.0 |
Resolution: | → fixed |
Status: | new → closed |
Landed, at long last, in [9e2f8933946a8f5bb2631209f1998b3d31ff42db]. The sets
issue was fixed a long time ago (and we no longer allow pythons that are old enough to need it anyways). Thanks!
Note: See
TracTickets for help on using
tickets.
Hrm. It looks like calling regular old twisted.python.failure.Failure.printTraceback with file=None will cause the lines of stack frames to be sent to twisted.python.log.msg, with an extra isError=1 marker. So we have a couple of choices:
I suppose it makes the most sense to send them to the twisted log.msg, using the same convention that Failure.printTraceback uses. That probably means we'll need to do something in call.py like: