Jean-Baptiste Barth 61bb550052 Ensure activity and decision tasks cannot progress on a closed workflow ... This is a second barrier because I'm a little nervous about this and I don't want moto/swf to make any activity progress while in the real world service, it's strictly impossible once the execution is closed. Python doesn't seem to have any nice way of freezing an object so here we go with a manual boundary...		2015-11-19 11:45:26 +01:00
..
__init__.py	Add WorkflowExecution.open to clarify code in some places	2015-11-19 11:45:26 +01:00
activity_task.py	Ensure activity and decision tasks cannot progress on a closed workflow	2015-11-19 11:45:26 +01:00
activity_type.py	Split SWF models into their own file	2015-11-19 11:45:22 +01:00
decision_task.py	Ensure activity and decision tasks cannot progress on a closed workflow	2015-11-19 11:45:26 +01:00
domain.py	Add WorkflowExecution.open to clarify code in some places	2015-11-19 11:45:26 +01:00
generic_type.py	Fix python 3.x compatibility regarding iterations on a dict	2015-11-19 11:45:26 +01:00
history_event.py	Implement start to close timeout on SWF workflow executions	2015-11-19 11:45:26 +01:00
workflow_execution.py	Add WorkflowExecution.open to clarify code in some places	2015-11-19 11:45:26 +01:00
workflow_type.py	Split SWF models into their own file	2015-11-19 11:45:22 +01:00