# Full example of Python sync worker

**URL:** <https://community.temporal.io/t/full-example-of-python-sync-worker/16941>\
**Category:** Community Support\
**Created:** [March 26, 2025, 9:17am UTC](https://community.temporal.io/t/full-example-of-python-sync-worker/16941 "2025-03-26T09:17:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![nakarin29](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/nakarin29/32/7178_2.png) [@nakarin29](https://community.temporal.io/u/nakarin29)\
**Post date:** [April 24, 2025, 4:46pm UTC](https://community.temporal.io/t/full-example-of-python-sync-worker/16941/6 "2025-04-24T16:46:44Z")

</div>

I think I have found the answer from [Temporal with synchronous python services](https://community.temporal.io/t/temporal-with-synchronous-python-services/11981)

Basically, your worker will still start in async mode and the workflows will still be running in async manner. However, you can run the sync activities by providing a threadpool when you create the worker. Ex [Temporal with synchronous python services](https://community.temporal.io/t/temporal-with-synchronous-python-services/11981)

```auto
    async with Worker(
        client,
        task_queue=<queue name>,
        workflows=<list of workflows>,
        activities=<list of activities>,
        activity_executor=ThreadPoolExecutor(5),
    ):

```

Then you can write all your activities without async keyword (aka running them in synchronously).

---

_[View the full topic](https://community.temporal.io/t/full-example-of-python-sync-worker/16941)._