> splitting state-impactful activity into its own function. Each separate state-impactful activity into its own function, no? > For the UI example... I wasn'

> splitting state-impactful activity into its own function. Each separate state-impactful activity into its own function, no? > For the UI example... I wasn't talking about building a GUI in a python program: I was talking about using python to automate an external GUI app. Because that toy example (which also happens to be done in the real world!) encapsulates a lot of the state issues that don't seem well-handled by the current design. Namely, that external interactions are a mix between stateless and stateful operations.