python-trio / python-trio/trio
Should run_sync_in_worker_thread count as a blocked task for wait_all_tasks_blocked / autojump_clock?
Open
Nobody has claimed this yet.
design discussion
pytest-trio relevant
threads
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
See some discussion here: https://gitter.im/python-trio/general?at=5a8f0962c3c5f8b90df08c95
CC: @sorcio
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
Start with the discussion linked in the issue, then inspect the implementations or entry points named by wait_all_tasks_blocked, autojump_clock, and run_sync_in_worker_thread. Determine whether worker-thread execution should count as a blocked task and document the expected behavior; the issue is complete when that behavior is resolved and represented in the relevant project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100