python-trio / python-trio/trio
Update introspection API for recent changes in nurseries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
-
Currently
nursery.startuses some tricky hacks internally that will lead to strange effects inInstrumenttracing. We should figure out what this should "look like" toInstruments, and make it happen.One option: show the child as directly showing up in the new nursery, as if it really were born there.
Another option: continue to show the current somewhat-wacky implementation details, but also expose a
task_movedevent. -
With the advent of simplified nurseries, I wonder if we should adjust our tracing code at all to better reflect the symmetry between the contents of the
withblock and the sibling tasks? For example, should we have trace events for nursery open/close? Should there be an entry innursery.child_taskswhile thewithblock is still open?
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
No files or tests are named. Start by reading nursery.start, the Instrument tracing behavior, and nursery.child_tasks; then clarify whether moved children, a task_moved event, nursery open/close events, or child_tasks entries are required. Done means the introspection API consistently reflects the chosen nursery model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100