python-trio / python-trio/trio
Debugging / introspection features
Open
Nobody has claimed this yet.
debugging
missing piece
user happiness
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
For quality of life:
- A method on
Taskto get a traceback - Ability to introspect set of all tasks (compare to thread iteration APIs)
- Give a task, quickly summarize what it's going. Curio has its "status" field. I don't like the manual bookkeeping this requires, and I think we can do better. Idea: walk the task's stack to find the innermost frame with a
__trio_wchan__local (or whatever), and report it as the wchan-equivalent. It could even be callable to get more details (e.g.run_in_worker_threadcould set it to print the repr of the call being run). Or I guess we'd get something similar by just showing the name+arguments of the frame. - An async REPL that provides little utilities based on things like the above to see what's going on in your program.
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 the existing Task API and comparing it with the thread iteration APIs mentioned in the issue; determine which introspection feature has a defined scope and acceptance criteria before proposing an implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100