Django

Code

Ticket #13080 (new)

Opened 5 months ago

Last modified 4 months ago

Documentation bug for Signal.connect

Reported by: george.sakkis@gmail.com Assigned to: nobody
Milestone: Component: Documentation
Version: 1.2-beta Keywords: signals
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Signal.connect says about the optional sender keyword "Must either be of type Signal, or None to receive events from any sender", but actually sender can be any any python object.

Attachments

Change History

03/10/10 19:30:55 changed by russellm

  • needs_better_patch changed.
  • stage changed from Unreviewed to Accepted.
  • needs_tests changed.
  • needs_docs changed.

To clarify: This is a comment about the docstring on Signal.connect, line 59 of django/dispatch/dispatcher.py

(Note for future reference -- if you're going to make a bug report, it helps to point out *where* the bug is)

03/18/10 07:00:03 changed by russellm

See #13132 for a related issue that requires clarification when the documentation surrounding sender is updated.

Add/Change #13080 (Documentation bug for Signal.connect)




Change Properties
Action