temporalio / temporalio/samples-python
Rework "hello" samples to separate starter and worker processes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 367
- Forks
- 121
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem? Please describe.
Initially we hoped the browse-ability of having several files right next to each other like normal Python scripts showing how things are done would be worth not doing the best practice of separating starters and workers (and just adding a comment to explain).
Describe the solution you'd like
Probably need a folder per sample with separate files for starter, worker, and maybe workflows, and maybe activities. Don't need to keep under "hello" and don't have to keep separate (e.g. can combine signals and queries).
Contributor guide
No contributing guide indexed for this repository
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
Start by inventorying the “hello” samples and their current starter, worker, workflow, and activity files. Define the intended per-sample layout and process boundaries with maintainers, then verify that each reorganized sample remains runnable and clearly demonstrates its intended pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100