python-trio / python-trio/trio
Trace origin of cancellations
Open
Nobody has claimed this yet.
cancellation
design discussion
user happiness
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
The reason for a cancellation isn't always obvious (multiple cancel scopes, timeouts, …). It should thus be possible to attach a traceback to a trio.Cancelled exception that can help discover its origin when debugging.
(Spin-off from https://github.com/python-trio/trio/issues/607)
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 reading the linked issue #607 and the cancellation-related parts of Trio to understand the existing scope and exception behavior. Define how a traceback should be attached to trio.Cancelled and what debugging result counts as complete; the issue does not name specific files or tests.
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
- 35/100