Günther Jena
Günther Jena
broqer should only allow immutable objects to be transfered. Having mutable objects transfered in a reactive way seems to be dangerous.
Any is implemented as CombineLatest and waits for all publishers to emit a value. Any should be True when *any* publisher evaluates to True.
A subscriber should know which publisher is subscribing. This will be called from publisher.subscribe(s)
Add it explicitly to Publisher to avoid warnings like this: 
It should not be a class method. Better would be re-using a Trace instance multiple times and using set_handler for this instance.
* e.g. https://python-broqer.readthedocs.io/en/latest/operators/combine_latest.py
MapAsync and MapThread are stateless and the first value emitted is after running the first coroutine/function. By adding an `init` argument the operator get's stateful with `init` as initial state....
When doing a method call on a publisher, the arguments of this call have to be constant: >>> v = Value('Hello World') >>> v.split(sep=' ') | op.Sink(print) ['Hello', 'World'] It...
Having examples of different applications would help understand the concepts. * wx/tk gui example * snake on console * RaspberryPi GPIO integration
Funny tool. After clicking `convert` on a multiline script I got one line. After clicking `convert` again the conversion is done a second time, but actually, it's not needed.