Py-Peeper
A very simple, minimalist, single-threaded and broadcast-routed approach to the observable pattern in Python.
Installation
pip install pypeeper
Usage
Implementing an Observable class
Every class can be converted to observable just by subclassing it from Observer. If class attribute "pattern" is overwritten with a valid regex expression, only matching attributes defined within the class constructor will be observed. Otherwise, all attributes will be observed.
from pypeeper import Observable, Observer
class AnyClass(Observable):
def __init__(self):
self.attribute_a = False
self.whatever_attr = 0
def set_attribute(self, value):
self.attribute_a = value
Implementing an Observer class
Any class can be Observer of all Observable classes defined as shown above. To define how the class should react on Observable's changes, just override "notify" method from Observer class.
class ObserverClass(Observer):
def notify(self, class_name, object_id, attribute_name, old, new):
print(class_name, object_id, attribute_name, old, new)
Instantiate and play
my_observable = AnyClass()
my_observer = ObserverClass()
my_observable.set_attribute(True)
my_observable.attribute_a = 10
my_observable.whatever_attr = None
Console output
>>> AnyClass 2448221506696 attribute_a False True
>>> AnyClass 2448221506696 attribute_a True 10
>>> AnyClass 2448221506696 whatever_attr 0 None
Metadata
Release files for pypeeper 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pypeeper-1.1-py3-none-any.whl | Python 3 | none | any | Details for pypeeper-1.1-py3-none-any.whl |
Release files / pypeeper-1.1-py3-none-any.whl
| Download URL | pypeeper-1.1-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be1c1e7f28ff9b089a23e31873e4a1e140699e73bf17b9ac8016bdb5507851de
|
|
BLAKE2b-256 checksum How to use checksums |
c5bd9bcf15b336084445db24328d1f9ff5847ac028cf63fd6c929d687a54fccc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.8
|
Security for pypeeper 1.1
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.