python-trio / python-trio/trio
could document explain some trio with ProactorEventLoop?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
The Document is very very informational. in https://trio.readthedocs.io/en/stable/design.html#inside-trio-core and https://github.com/python-trio/trio/issues/52, it seems trio hasn't used IOCP too much. But there's asyncio.ProactorEventLoop in stdlib with IOCP.
can't trio use that wheel? is this the useful information and may add a few explanations to the Document?
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 Trio design documentation at design.html#inside-trio-core and the discussion in issue #52, then compare their explanation with Python's asyncio.ProactorEventLoop and IOCP. Done means determining whether this relationship is relevant to Trio and identifying the specific explanation the documentation should provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100