Metadata-Version: 2.1
Name: fluidstate
Version: 1.0.0b1
Summary: Compact state machine in Python that can be vendored.
Home-page: https://github.com/kuwv/python-fluidstate
License: MIT
Keywords: state machine,dsl
Author: Jesse P. Johnson
Author-email: jpj6652@gmail.com
Requires-Python: >=3.6.2,<4.0.0
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: Software Development :: Libraries
Project-URL: Repository, https://github.com/kuwv/python-fluidstate
Description-Content-Type: text/x-rst

Fluidstate
==========

Compact state machine that can be vendored.


How to use
----------

A very simple example taken from specs::

    from fluidstate import StateMachine, state, transition

    class SimpleMachine(StateMachine):

         initial_state = 'created'

         state('created')
         state('waiting')
         state('processed')
         state('canceled')

         transition(before='created', event='queue', after='waiting')
         transition(before='waiting', event='process', after='processed')
         transition(before=['waiting', 'created'], event='cancel', after='canceled')


"A slightly more complex example"
---------------------------------

For demonstrating more advanced capabilities::

        from fluidstate import StateMachine, state, transition

        class Relationship(StateMachine):
            initial_state = (
                lambda relationship: relationship.strictly_for_fun() and 'intimate' or 'dating'
            )

            state('dating', on_entry='make_happy', on_exit='make_depressed')
            state('intimate', on_entry='make_very_happy', on_exit='never_speak_again')
            state('married', on_entry='give_up_intimacy', on_exit='buy_exotic_car')

            transition(before='dating', event='get_intimate', after='intimate', need='drunk')
            transition(
                before=['dating', 'intimate'],
                event='get_married',
                after='married',
                need='willing_to_give_up_manhood'
            )

            def strictly_for_fun(self) -> None:
                pass

            def drunk(self) -> bool:
                return True

            def willing_to_give_up_manhood(self) -> bool:
                return True

            def make_happy(self) -> None:
                pass

            def make_depressed(self) -> None:
                pass

            def make_very_happy(self) -> None:
                pass

            def never_speak_again(self) -> None:
                pass

            def give_up_intimacy(self) -> None:
                pass

            def buy_exotic_car(self) -> None:
                pass


States
------

A Fluidstate state machine must have one initial state and at least one other additional state.

A state may have pre and post callbacks, for running some code on state *on_entry*
and *on_exit*, respectively. These params can be method names (as strings),
callables, or lists of method names or callables.


Transitions
-----------

Transitions lead the machine from a state to another. Transitions must have
*before*, *after*, and *event* parameters. *before* is one or more (as list) states
from which the transition can be preed. *after* is the state to which the
transition will lead the machine. *event* is the method that have to be called
to launch the transition. This method is automatically created by the Fluidstate
engine.

A transition can have optional *trigger* and *need* parameters. *trigger* is a
method (or callable) that will be called when transition is launched. If
parameters are passed to the event method, they are passed to the *trigger*
method, if it accepts these parameters. *need* is a method (or callable) that
is called to allow or deny the transition, depending on the result of its
execution. Both "trigger" and *need* can be lists.

The same event can be in multiple transitions, going to different states, having
their respective needs as selectors. For the transitions having the same event,
only one need should return a true value at a time.


Individuation
-------------

States and transitions are defined in a class-wide mode. However, one can define
states and transitions for individual objects. For example, having "door" as a
state machine::

    door.add_state('broken')
    door.add_transition(event='crack', before='closed', after='broken')


These additions only affect the after object.


Install
-------

Run::

    pip install fluidstate


Test
----

Rn::

    tox


Attribution
-----------

Fluidstate is forked from https://github.com/nsi-iff/fluidity created by Rodrigo Manhães.

