You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/develop/python/python-sdk-sync-vs-async.mdx
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,8 +77,6 @@ Python workers have following components for executing code:
77
77
78
78
> See Also: [docs for](https://python.temporal.io/temporalio.worker.Worker.html#__init__)`worker.__init__()`
79
79
80
-
81
-
82
80
### Activities
83
81
84
82
- The activities and the temporal worker SDK code both run in whatever event loop the user gives the worker (which is often the default asyncio event loop).
@@ -103,8 +101,7 @@ The only ways to use more than one CPU core in a python worker (considering the
103
101
### Separating Activity and Workflow Workers
104
102
105
103
To reduce the risk of event loops or executors getting blocked,
106
-
some users choose to deploy separate workers for workflow tasks and activity tasks.
107
-
104
+
some users choose to deploy separate workers for workflow tasks and activity tasks.
0 commit comments