1.4.2

Transitions are no longer duplicated when calling copy_from_statechart (see #91 & #92), thanks to Jan Wouter Versluis!

1.4.1

The internals required to expose time and event-related predicates in a PythonEvaluator are moved
to the Interpreter instead of being handled by context providers. This eases the implementation by other
code evaluators of uniform semantics for these predicates. This change does not affect Sismic public API.

New binding/monitoring & event processing

1.4.0

Prepare 1.4.0

Transition priorities, clock-based time, queued events and runners

1.3.0

Fix MockedRunner in tests for Python 3.4

Event should not be exposed when evaluating guards of eventless transitions

1.2.2

Changelog

Prevent useless guard evaluations

1.2.1

Prepare for 1.2.1

Notify bound properties with user-defined meta-events

Add a notify function to the Python code evaluator. This function allows users to create user-defined meta-events that are propagated to bound property statecharts. See #66 for more information.

1.1.2 - interpreter serialization

Interpreter instances can be serialized using pickle (#66).

1.1.1

Whitespaces in event parameters used in BDD steps are stripped before they are evaluated.

1.1.0 - Final states

Final states remain in the active configuration unless they are all children of the root state. In this case, statechart execution is stopped. Previously, if all leaf states of the active configuration were final states, the execution stopped even if these final states were nested in an orthogonal or compound state. The corrected behavior strictly adheres to SCXML 1.0 semantics. This could be a backward incompatible change if you explicitly relied on the previously wrong behaviour.