Giter Site home page Giter Site logo

observable's Introduction

observable

Build Status Code style: black

pyobservable is a minimalist event system for python. It provides you an easy-to-use interface to trigger arbitrary functions when specific events occur.

from observable import Observable

obs = Observable()

@obs.on("error")
def error_handler(message):
    # do some fancy error handling
    logging.error(f"An error occured: {message}")

...

def do_time_travel():
    # do some time traveling
    ...
    if year != 1291:
        obs.trigger("error", "Time travel to 1291 didn't work")

An ObservableProperty type is included as well, which makes observing object properties a breeze.

Note: We are Python 3 only! Only Python Versions >= 3.5 are supported. Use v0.3.2 for older Python Versions.

How to use

Use a pip to install it from PyPI:

pip install observable

After completion you can start using observable:

from observable import Observable

obs = Observable()

Usage of observable.Observable

on: Register event handler with on

There are two ways to register a function to an event.
The first way is to register the event with a decorator like this:

@obs.on("error")
def error_func(message):
    print("Error: %s" % message)

The second way is to register it with a method call:

def error_func(message):
    print("Error: %s" % message)
obs.on("error", error_func)

once: Register event handler with once

once works like on, but once the event handler is triggered it will be removed and cannot be triggered again.

trigger: trigger event

You can trigger a registered event with the trigger method:

obs.trigger("error", "This is my error message")

If no handler for the event error could be found an Observable.NoHandlerFound-Exception will be raised.

off: remove handler and events

Remove a handler from a specified event:

obs.off("error", error_func)
obs.off("error", [error_func, second_error_func])

Remove all handlers from a specified event:

obs.off("error")

Clear all events:

obs.off()

get_all_handlers, get_handlers and is_registered: Check which handlers are registered

Imagine you registered the following handlers:

@obs.on("success")
def success_func():
    print("Success!")

@obs.on("error")
def error_func(message):
    print("Error: %s" % message)

Then you can do the following to inspect the registered handlers:

>>> obs.get_all_handlers()
{'success': [<function success_func at 0x7f7f32d0a1e0>], 'error': [<function error_func at 0x7f7f32d0a268>]}
>>> obs.get_handlers("success")
[<function success_func at 0x7f7f32d0a1e0>]
>>> obs.get_handlers("other_event")
[]

Usage of observable.property.ObservableProperty

A property that can be observed easily by listening for some special, auto-generated events. Its API is identical to that of the build-in property.

The ObservableProperty needs an Observable object for triggering events. If the property is an attribute of an object of type Observable, that one will be used automatically. To specify a different Observable object, pass it as the observable keyword argument when initializing the ObservableProperty. You may also pass a string for observable, which looks for an attribute of that name in the containing object. This is useful to specify the name of an attribute which will only be created at object initialization and thus isn't there when defining the property.

The following events, of which "after_set_<name>" is probably the one used most, are triggered:

  • "before_get_<name>"() and "after_get_<name>"(value)
  • "before_set_<name>"(value) and "after_set_<name>"(value)
  • "before_del_<name>"() and "after_del_<name>"()

<name> has to be replaced with the property's name. Note that names are taken from the individual functions supplied as getter, setter and deleter, so please name those functions like the property itself. Alternatively, the name to use can be specified with the name keyword argument when initializing the ObservableProperty.

The convenience helper ObservableProperty.create_with() can be used as a decorator for creating ObservableProperty objects with custom event and/or observable. It returns a functools.partial() with the chosen attributes pre-set.

Here's an example for using the event and observable keyword arguments:

>>> from observable import Observable
>>> from observable.property import ObservableProperty
>>> class MyObject:
...     def __init__(self):
...         self.events = Observable()
...         self._value = 10
...     @ObservableProperty.create_with(event="prop", observable="events")
...     def some_obscure_name(self):
...         return self._value
...     @some_obscure_name.setter
...     def some_obscure_name(self, value):
...         self._value += value
...
>>> obj = MyObject()
>>> obj.obs.on("after_get_prop", lambda v: print("got", v))
>>> obj.obs.on("before_set_prop",
...            lambda v: print("setting", obs.some_obscure_name, v))
>>> obj.obs.on("after_set_prop", lambda v: print("set", v))
>>> obj.some_obscure_name = 32
got 10
setting 10 32
set 32
>>> obj.some_obscure_name
got 42
42

This project is published under MIT.
A Timo Furrer project.
- ๐ŸŽ‰ -

observable's People

Contributors

daa avatar gitter-badger avatar marcinn avatar michaelwills avatar timofurrer avatar yardanico avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

observable's Issues

Observable properties

Hi,

What do you think about an API for observing properties easily? This would allow something like the following:

>>> import observable as obs
>>> class A(obs.Observable):
...   @obs.ObservableProperty
...   def x(self): return 42
...   @x.setter
...   def x(self, val): pass
... 
>>> a=A()
>>> a.on("x_get", lambda x:print("get",x))
<function <lambda> at 0x7fa793345f28>
>>> a.on("x_set", lambda x:print("set",x))
<function <lambda> at 0x7fa792ae8d90>
>>> a.x
get 42
42
>>> a.x=5
set 5

The ObservableProperty is a child of the built-in property that wraps the getter, setter and deleter to trigger appropriate events on the holding object whenever they are called.

I have an implementation at hand which I could submit as a PR, if desired.

The exact event types and names like "x_get", "x_del" have to be discussed, of course.

Best regards
Robert

Licensing under an open source license

Hi,

Thanks for this handy library! It's perfect for simple use cases like mine.

However, I'd like to use it in a project under Apache License, which can't be changed. Don't get me wrong, I like the GPL a lot for complex works, but for such basic libraries like pyobservable it dramatically limits the possible use cases.

I'm writing this because many software authors are simply not aware of the implications resulting from their license choice. If you want to limit the usage of this library to projects using the GPL, that's fine and you can close the issue. But if not, it'd be better to license under Apache V2, for instance.

What do you think?

Best regards
Robert

Observable collections

I would like to have observable dicts to notify on item add/remove. This seems like a pattern that observable might want to provide an implementation for, and/or docs with a recipe for observing core collection types. If the core types need to be subclassed in order to be observed, a helper/mixin would be useful to make it easy.

Modifying registrations from inside an event handler causes unexpected behaviour

Hello,

I already submitted a PR to fix this, but here comes the corresponding issue.

When triggering an event, the loop goes over the registered handlers and calls them one after another. But when one of these handlers changes the list of registered handlers (e.g. by calling off() like the once() wrapper does), the trigger loop gets disordered andcan skip handlers or execute them twice. Demonstrations for this are provided in the comments of the PR.

My proposed solution for this is creating a working copy of the list of event handlers to iterate over.

See #8.

Best regards
Robert

New release incl. ObservableProperty

Hiya thanks for this library, I like its usability/API a lot!

Any chance to cut an official release that includes the ObservableProperty feature? It's been a while since it was added. Didn't knew I'd needed it before I stumbled upon it, but now I really do! :-)

How to obtain trigger callback returns

First, thanks for this neat package! It looks like it's not possible to obtain the return value of the triggered callbacks as trigger('foo') always returns True.

However, I think it would be nice to have this option to use callbacks to influence the control flow. Consider the following example where an event is triggered in a save method.

def save(data):
      observable.trigger('save', data)
      with open('bla.txt') as f: 
           f.write(data)
# ...

observable.on('save', lambda data: True)

The user can hook into the save method but the callback cannot send anything back to influence what's happening at the trigger point, like here:

def save(data):
      if observable.trigger('save', data) is False:
          return
      with open('bla.txt') as f: 
           f.write(data)
# ...

def custom_save(data):
      with open('a_differnt_save_method.txt') as f:
            f.write(data)
      return False   # returns False to prevent execution of default save logic

observable.on('save', custom_save)

If trigger would collect the callback returns such 'extension via event' could be implemented. Would you consider enhancing the trigger behaviour?

Release of v1.0.1 on PyPi

Hi,

is there a reason why v1.0.1 hasn't been pushed to PyPi yet? I'm pulling it as a dependency in one of my packages and still get v0.3.2 without the fixes around once() etc.

Best regards
Robert

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.