I appreciate the response.
You are defining a custom create method on the Model class, and then dispatching the actual creation to the model Manager anyway. This is bad design — managers and
.create()exist for a reason, so subclass and override them confidently
Thanks for the reply —very interesting.
I haven’t dug too deep into
django-fsm, mostly browsed the code for inspiration.
Using the “lightweight” optimistic approach (as you call it) — does it mean I cannot reliably implement an action that dont trigger a state…