Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#26493 closed Cleanup/optimization (fixed)

Document that built-in signals use send()

Reported by: Kevin Christopher Henry Owned by: Filipa Andrade
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

I think that Django consistently uses send() rather than send_robust() for its built-in signals, but it's not mentioned in ​the documentation.

The distinction matters to application code that uses these signals, since it determines whether or not a raised Exception will propagate.

Change History (6)

comment:1 by Tim Graham, 8 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by Filipa Andrade, 8 years ago

Owner: changed from nobody to Filipa Andrade
Status: new → assigned

comment:3 by Filipa Andrade, 8 years ago

Added documentation available in ​https://github.com/django/django/pull/6449

Last edited 8 years ago by Tim Graham (previous) (diff)

comment:4 by Tim Graham, 8 years ago

Has patch: set
Triage Stage: Accepted → Ready for checkin

comment:5 by Tim Graham <timograham@…>, 8 years ago

Resolution: → fixed
Status: assigned → closed

In 47fbbc33:

Fixed #26493 -- Documented how built-in signals are sent.

comment:6 by Tim Graham <timograham@…>, 8 years ago

In 8bf5ced:

[1.9.x] Fixed #26493 -- Documented how built-in signals are sent.

Backport of 47fbbc33de805c803c39483344854caa2890c32c from master

Note: See TracTickets for help on using tickets.
Back to Top