temporalio / temporalio/samples-python
[Feature Request] Properly shutdown executors when done using them
Open
Nobody has claimed this yet.
enhancement
- 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.
Right now in hello_activity_threaded.py and hello_activity_multiprocess.py we are not properly shutting down the executors and we should be.
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 reading hello_activity_threaded.py and hello_activity_multiprocess.py, focusing on how each executor is created and used. Update both samples so the executors are properly shut down when finished, then run the relevant samples to verify they complete cleanly without leaving executor work active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100