Ticket #136 (closed enhancement: wontfix )

Opened 7 years ago

Last modified 7 months ago

Verbose mode for logging

Reported by: itamarst Assigned to: glyph
Type: enhancement Priority: low
Milestone: Component: core
Keywords: easy Cc: glyph, itamarst
Branch: Author:
Launchpad Bug:

Attachments

Change History

  2003-07-28 06:11:37+00:00 changed by itamarst

Turns on logging of locals/globals and all extra info
Failures have that is *not* logged by default. This would be
done for specific log observers, most notably the default
logfile/stderr log observer.

  2003-08-03 06:03:01+00:00 changed by glyph

what the heck, I'll pick this one up

  2005-10-27 13:23:32+00:00 changed by glyph

*27 months* of inactivity?  Fiddlesticks.  This definitely isn't important.

  2009-01-01 17:09:05+00:00 changed by exarkun

  • keywords set to easy
  • component set to core
  • launchpad_bug deleted
  • branch deleted
  • branch_author deleted

I suggest implementing this as an optional argument to FileLogObserver about the verbosity of the failure logging to perform. FileLogObserver.emit can pass this option on to textFromEventDict which can pass it on when it calls getTraceback. Since log observers can be customized in tac files now, this will let people create a log observer using any verbosity they like. However, it may also be nice to add this to the twistd command line, either by including it along with --debug, or adding a separate --log-verbose-failures option, or both.

Or perhaps this is a worthless feature. I can't really think of any times when I have desired this. I generally go straight to pdb when debugging. It's easier to find the precise thing I'm looking for. Verbose failure logging forces one to search through a big mountain of data.

  2009-06-30 09:22:18+00:00 changed by glyph

  • status changed from new to closed
  • resolution set to wontfix

I'm going to go ahead and agree with exarkun that this just isn't that important. In the rare cases where I want insanely verbose logging, I want --spew, and we've got that.

Note: See TracTickets for help on using tickets.