temporalio / temporalio/sdk-python
Why are synchronous activities recommended?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
from README.md:
The
say_hello_activityis synchronous which is the recommended activity type (see "Types of Activities" below), but it can beasync
However a few lines below, asynchronous activities are described as much more performant. Also, handling any sync tasks requires the Worker to be created with an explicit executor parameter.
It seems like async activities are expected and sync ones should be exceptional.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read README.md, starting with the say_hello_activity example and the “Types of Activities” section. Compare the recommendation for synchronous activities with the performance guidance and executor requirement, then clarify the documentation so the intended default and exceptions are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100