python-trio / python-trio/trio
Raise RecursionError if nurseries are too nested
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
We should pretend that the call stack a nursery is in is added to any child tasks. While this is somewhat flimsy (we will only be able to check the call stack size when creating a new nursery), it will prevent some simple issues w/r/t recursion.
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 by tracing nursery creation and how child tasks inherit or check call-stack state; the issue does not name specific files or tests. Clarify the intended recursion limit and failure behavior, then add coverage showing that excessively nested nurseries raise RecursionError without affecting valid nesting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100