Alexandre Decan

The first (above) discussion dates back to 2014. The second one was created this year, in March. I hope it will receive more feedback :)

Introduced in 0.22.0, removed in 0.23.0. Kept in that branch for posterity.

Hello, Saving and loading statecharts at runtime is not part of what Sismic offers at the moment. I do understand how interesting this can be, but providing official support for...

The context providers are used by the code evaluator to help providing e.g. time-related predicates in the context that is exposed by the code evaluator. Previously, all these predicates were...

I would say that if you're not afraid of digging into Sismic internals, the "easiest" way (the more straightforward one) is probably to manually override the content of `_configuration` in...

I quickly tried to move the internals required by time and event-related predicates to the `Interpreter` instead of context providers. It was quite easy to make the current `PythonEvaluator` work...

The changes are included in Sismic 1.4.1. It will be available on PyPI in a few minutes.

I think queues are to be saved as well, because Sismic supports "future events", so we can have events in the queue that are not yet processed because the current...

The same holds for the execution context: it can contain any python object, even the ones that are not serializable. Pickling should be applied for them in that case, but...

@abidoul Should we keep this issue opened? I don't have any short-term solution to propose...