Green Rocket
Green Rocket is a simple and compact implementation of Observer (or Publish/Subscribe) design pattern via signals.
Create specific signal using base one:
>>> from greenrocket import Signal
>>> class MySignal(Signal):
... pass
...
Subscribe handler:
>>> @MySignal.subscribe
... def handler(signal):
... print('handler: ' + repr(signal))
...
Fire signal:
>>> MySignal().fire()
handler: MySignal()
If you are using asyncio, you can also use coroutines as handlers and fire signal asynchronously using await Signal.afire() or yield from Signal().afire(). Method afire() works well with synchronous handlers too.
Note, that signal propagates over inheritance, i.e. all subscribers of base signal will be called when child one is fired:
>>> @Signal.subscribe
... def base_handler(signal):
... print('base_handler: ' + repr(signal))
...
>>> MySignal().fire()
handler: MySignal()
base_handler: MySignal()
Unsubscribe handler:
>>> MySignal.unsubscribe(handler)
>>> MySignal().fire()
base_handler: MySignal()
The handler is subscribed using weak reference. So if you create and subscribe a handler in local scope (for example inside a generator), it will be unsubscribed automatically.
>>> def gen():
... @MySignal.subscribe
... def local_handler(signal):
... print('local_handler: ' + repr(signal))
... yield 1
...
>>> for value in gen():
... MySignal(value=value).fire()
...
local_handler: MySignal(value=1)
base_handler: MySignal(value=1)
>>> import gc # PyPy fails the following test without
>>> _ = gc.collect() # explicit call of garbage collector.
>>> MySignal(value=2).fire()
base_handler: MySignal(value=2)
>>> Signal.unsubscribe(base_handler)
As you can see above, signal constructor accepts keyword arguments. These arguments are available as signal’s attributes:
>>> s = MySignal(a=1, b=2)
>>> s.a
1
>>> s.b
2
Signal suppresses any exception which is raised on handler call. It uses logger named greenrocket from standard logging module to log errors and debug information.
The library also provides Watchman class as a convenient way for testing signals.
Create watchman for specific signal:
>>> from greenrocket import Watchman
>>> watchman = Watchman(MySignal)
Fire signal:
>>> MySignal(x=1).fire()
Test signal:
>>> watchman.assert_fired_with(x=1)
>>> watchman.assert_fired_with(x=2) # DOCTEST: +ellipsis
Traceback (most recent call last):
...
AssertionError: Failed assertion on MySignal.x: 1 != 2
>>> watchman.assert_fired_with(x=1, y=2) # DOCTEST: +ellipsis
Traceback (most recent call last):
...
AssertionError: MySignal has no attribute y
Watchman object saves each fired signal to its log:
>>> watchman.log
[MySignal(x=1)]
>>> MySignal(x=2).fire()
>>> watchman.log
[MySignal(x=1), MySignal(x=2)]
The method assert_fired_with tests the last signal from the log by default:
>>> watchman.assert_fired_with(x=2)
But you can specify which one to test:
>>> watchman.assert_fired_with(-2, x=1)
CHANGES
0.30
Added Signal.afire() method that returns awaitable to support coroutine-based signal handlers
Dropped Python 2.6 and 3.2 support
0.22
Added Watchman class as a testing helper
0.21
Removed distribute dependency
Improved tests
0.20
Changed handler subscription mechanism from subscription by reference to subscription by weak reference
0.11
Fixed logger loose on program termination
0.1
Initial release
Metadata
Release files for GreenRocket 0.30
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 | |
|---|---|---|---|---|
| GreenRocket-0.30.tar.gz | 5.4 kB | Without provenance | Details |
Release files / GreenRocket-0.30.tar.gz
| Download URL | GreenRocket-0.30.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57a729e8a3d31e34f1eabed3570a34645d7f38cefb4678d809cead293720dbae
|
|
BLAKE2b-256 checksum How to use checksums |
b68b55faeb7889eed5d22b467e17380f966aea5aa97484a79990aaee80f51af9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for GreenRocket 0.30
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.