automat

package documentation

(source)

State-machines.

Module	`_core`	A core state-machine abstraction.
Module	`_discover`	No module docstring; 4/4 functions, 3/3 exceptions documented
Module	`_introspection`	Python introspection helpers.
Module	`_methodical`	No module docstring; 0/2 variable, 0/2 type alias, 0/2 type variable, 7/10 functions, 3/4 classes documented
Module	`_runtimeproto`	Workaround for the lack of TypeForm.
Package	`_test`	No package docstring; 1/6 module documented
Module	`_typed`	No module docstring; 0/3 variable, 0/2 type alias, 0/5 type variable, 0/3 constant, 1/1 function, 8/10 classes documented
Module	`_visualize`	No module docstring; 4/7 functions documented

From __init__.py:

Class	`MethodicalMachine`	A `MethodicalMachine` is an interface to an `Automaton` that uses methods on a class.
Class	`TypeMachine`	A `TypeMachine` is a factory for instances of `InputProtocol`.
Class	`TypeMachineBuilder`	The main entry-point into Automat, used to construct a factory for instances of `InputProtocol` that take an instance of `Core`.
Exception	`AlreadyBuiltError`	The `TypeMachine` is already built, and thus can no longer be modified.
Exception	`NoTransition`	A finite state machine in `state` has no transition for `symbol`.
Function	`pep614`	This is a workaround for Python 3.8, which has some restrictions on its grammar for decorators, and makes `@state.to(other).upon(Protocol.input)` invalid syntax; for code that needs to run on these older Python versions, you can do ...

def pep614(t: R) -> R: (source) ¶

This is a workaround for Python 3.8, which has some restrictions on its grammar for decorators, and makes @state.to(other).upon(Protocol.input) invalid syntax; for code that needs to run on these older Python versions, you can do @pep614(state.to(other).upon(Protocol.input)) instead.