python-trio / python-trio/trio
Making the use of Multiple interpreters simple
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
Woudn't it be interesting for the "simplicity of usage" minds behind trio to look on how to exploit multiple-interpreters ?
Python-3.12 is upon us but there won't be any meaningfull standard use of multiple interpreters till 3.13
.... it would look like a perfect space window for imagination again.
it's a bit like writing to santa, but who knows.
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 issue context alongside Trio's current concurrency documentation and Python's multiple-interpreter support for Python 3.13. The issue names no files, tests, or entry points; a concrete scope, implementation approach, and verifiable definition of done would need to be established before coding.
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
- 20/100