Support observe as a decorator outside of classes
- Lenguaje dominante
- Python
- Estrellas
- 653
- Forks
- 217
- Merge medio
- 2 d 21 h
- PR fusionados (30 d)
- 2
Descripción
Please note that I have only used `traitlets` as a part of `ipywidgets`, and not sure how feasible are the suggestions below for its other uses - but for widgets they would be quite useful.
So, when one needs to `observe` a widget trait, it can't be done without separately defining the handler function and then subscribing:
``` python
def handler(*_):
# ... code ...
w.observe(handler, 'value')
```
Wouldn't it be better if you could just write like this:
``` python
@w.observe('value')
def _(*_):
# ... code ...
```
This way there is also no need to make a name for the handle function.
However, it's often useful to call the handler once after setting everything up, e.g. if you make some plots in the handler it makes sense to display them without forcing user to move a slider or something. So, I also suggest adding an argument to `observe`, like `run=True` (looking for a better name :) ) or a separate method `observe_and_run` which would also execute the handler (in addition to subscribing). This way we still wouldn't have to think of a name for the handler function.
So, instead of:
``` python
def handler(*_):
# ... code ...
w.observe(handler, 'value')
handler()
```
we would be able to write:
``` python
@w.observe('value', run=True)
def _(*_):
# ... code ...
```
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.