Nothing like set_state("string") for transitions

1. Both transitions and states can be added via strings
2. states can be reached via strings

Still I did not find a method in core.py to reach a transition via string. In my opinion a necessary feature to use transitions for APIs where triggers get passed via string.

Currently I’m doing

def _set_transition(self, name): eval('self.' +name+'()') self._set_transition("string")

to all my classes. But It would be great to have

self.machine.set_transition("string")

instead.

[tyarkoni]

Well, one limitation (though it’s actually a feature and not a bug) of set_state() is that it won’t cause any of the callbacks to fire. It’ll just immediately move the model to the specified state. So you don’t want to use set_state() if you need the callbacks to do stuff for you. I would probably go with the getattr approach above.

On further reflection though, I do think it probably makes sense to have an easy way to trigger events from the model by passing a string. While the approach I suggested above works fine, the user shouldn’t really have to reach inside the model that way. @aleneum and @wtgee, any objections to my adding a trigger() method to the Model?

[aleneum]

It was a welcome way to distract myself from something I (don’t) want to do today 😉. And closing tickets is fun (sorry for taking that away). BUT… stumbled upon a pygraphviz issue which occurs sometimes -_- Update: Best way to work around error message generation issues is to prevent errors 🙈