Opened 17 years ago
Closed 17 years ago
#5910 closed (wontfix)
Signals are unnamed making logging non-informative
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | smurf@… | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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 (1)
Change History (4)
by , 17 years ago
| Attachment: | signals.patch added |
|---|
comment:1 by , 17 years ago
| Cc: | added |
|---|
comment:2 by , 17 years ago
| Summary: | [patch] Signals are unnamed → Signals are unnamed making logging non-informative |
|---|---|
| Triage Stage: | Unreviewed → Ready for checkin |
comment:3 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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."