*November 5, 2024*This release introduces powerful new features for the `StateMachine`library: {ref}`Condition expressions` and explicit definition of{ref}`Events`. These updates make it easier to define complex transitionconditions and enhance performance, especially in workflows with nestedor recursive event structures.StateMachine 2.4.0 supports Python 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, and3.13.This release introduces support for conditionals with Boolean algebra.You can now use expressions like `or`, `and`, and `not` directly withintransition conditions, simplifying the definition of complex statetransitions. This allows for more flexible and readable condition setupsin your state machine configurations.Example (with a spoiler of the next highlight):```py>>> from statemachine import StateMachine, State, Event>>> class AnyConditionSM(StateMachine):...     start = State(initial=True)...     end = State(final=True)......     submit = Event(...         start.to(end, cond="used_money or used_credit"),...         name="finish order",...     )......     used_money: bool = False...     used_credit: bool = False>>> sm = AnyConditionSM()>>> sm.submit()Traceback (most recent call last):TransitionNotAllowed: Can't finish order when in Start.>>> sm.used_credit = True>>> sm.submit()>>> sm.current_state.id'end'``````{seealso}See {ref}`Condition expressions` for more details or take a look at the{ref}`sphx_glr_auto_examples_lor_machine.py` example.```Now you can explicit declare {ref}`Events` using the {ref}`event` class.This allows custom naming, translations, and also helps your IDE to knowthat events are callable.```py>>> from statemachine import StateMachine, State, Event>>> class StartMachine(StateMachine):...     created = State(initial=True)...     started = State(final=True)......     start = Event(created.to(started), name="Launch the machine")...>>> [e.id for e in StartMachine.events]['start']>>> [e.name for e in StartMachine.events]['Launch the machine']>>> StartMachine.start.name'Launch the machine'``````{seealso}See {ref}`Events` for more details.```We removed a note from the docs saying to avoid recursion loops. Sincethe {ref}`StateMachine 2.0.0` release we've turned the RTC model enabledby default, allowing nested events to occour as all events are put on aninternal queue before being executed.```{seealso}See {ref}`sphx_glr_auto_examples_recursive_event_machine.py` for anexample of an infinite loop state machine declaration using `after`action callback to call the same event over and over again.```- Fixes  [#484](#484)issue where nested events inside loops could leak memory by incorrectly  referencing previous `event_data` when queuing the next event. Thisfix improves performance and stability in event-heavy workflows.

* docs: mention pydot resolution settings---------Co-authored-by: Albert Latham <albertlatham@gladiatortechnologies.com>

#519)

* Sanitise project path on windows for doc build* MachineScraper now uses regex escape function for robustness