Blinker
Blinker provides a fast dispatching system that allows any number of interested parties to subscribe to events, or “signals”.
Signal receivers can subscribe to specific senders or receive signals sent by any sender.
>>> from blinker import signal >>> started = signal('round-started') >>> def each(round): ... print "Round %s!" % round ... >>> started.connect(each)>>> def round_two(round): ... print "This is round two." ... >>> started.connect(round_two, sender=2)>>> for round in range(1, 4): ... started.send(round) ... Round 1! Round 2! This is round two. Round 3!
Requirements
Blinker requires Python 2.4 or higher, Python 3.0 or higher, or Jython 2.5 or higher.
Changelog Summary
- 1.2 (October 26, 2011)
Added Signal.receiver_connected and Signal.receiver_disconnected per-Signal signals.
Deprecated the global ‘receiver_connected’ signal.
Verified Python 3.2 support (no changes needed!)
- 1.1 (July 21, 2010)
Added @signal.connect_via(sender) decorator
Added signal.connected_to shorthand name for the temporarily_connected_to context manager.
- 1.0 (March 28, 2010)
Python 3.x compatibility
- 0.9 (February 26, 2010)
Sphinx docs, project website
Added with a_signal.temporarily_connected_to(receiver): ... support
Metadata
Release files for blinker 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| blinker-1.2.tar.gz | 66.2 kB | Without provenance | Details |
Release files / blinker-1.2.tar.gz
| Download URL | blinker-1.2.tar.gz |
|---|---|
| Size | 66.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7062c05e9f724e2208835e335df5ffdc169004fe372ca91fb6408cd0f8e3aa85
|
|
BLAKE2b-256 checksum How to use checksums |
bf92b8c23de91e995d0f0245c5ebbae0e8a803bc1811be15921258a15efa1df5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for blinker 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
