Django

Code

Ticket #5910 (closed: wontfix)

Opened 6 months ago

Last modified 5 months ago

Signals are unnamed making logging non-informative

Reported by: smurf@smurf.noris.de Assigned to: nobody
Component: Core framework Version: SVN
Keywords: Cc: smurf@smurf.noris.de
Triage Stage: Ready for checkin Has patch: 1
Needs documentation: 0 Needs tests: 0
Patch needs improvement: 0

Description

When debugging, I frequently need to log signals. However, they're just opaque objects: figuring out *which* signal is logged is frequently very very annoying.

Therefore I propose this simple patch.

Attachments

signals.patch (1.4 kB) - added by smurf@smurf.noris.de on 11/09/07 03:28:29.

Change History

11/09/07 03:28:29 changed by smurf@smurf.noris.de

  • attachment signals.patch added.

11/09/07 03:29:35 changed by anonymous

  • cc set to smurf@smurf.noris.de.
  • needs_better_patch changed.
  • needs_tests changed.
  • needs_docs changed.

12/01/07 19:35:43 changed by Simon G <dev@simon.net.nz>

  • summary changed from [patch] Signals are unnamed to Signals are unnamed making logging non-informative.
  • stage changed from Unreviewed to Ready for checkin.

12/20/07 22:49:26 changed by jdunck

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

Quoting Malcolm on #4521, of which this is a dupe, "We're going to end up taking some variation on #4561 and that includes this functionality. So let's punt this exact patch and push the other one to completion."

Add/Change #5910 (Signals are unnamed making logging non-informative)




Change Properties
Action