Question about multiple destination [concurrency]

I know that multiple source is correct and defined as follow:

transition_1 =  {'trigger': 'jump', 'source': ['a','b'], 'dest': 'c'}

But when it comes to multiple destination, it’s wrong.

transition_2 = {'trigger': 'jump', 'source': 'a', 'dest': ['b','c']}

I don’t know how to implement using this library. Anyone can give me some ideas? or add this feature to this library? Welcome to discuss.

[aleneum]

Since the above mentioned ‘workaround’ does not satisfy proper concurrency, I add ‘concurrent states’ as a feature for 0.7.0. This requires some significant changes in the nested states extension but I assume this tradeoff should be worth it since there is a lack of (Python) state machine libraries that support concurrency.

[aleneum]

transition 0.8.0 now supports parallel states as mentioned and illustrated in #371. Having parallel states is solved by using nested states with the parallel keyword.

Transitions with mutliple destinations are not supported though. I opted for the nested solution since this is how it is defined in state charts as far as I can tell and I could also not think of a custom transitions-way of definining scopes and how to determine when concurrent states should be exited again.