python-trio / python-trio/trio
Windows: improve usability for low-level IOCP operations
Open
Nobody has claimed this yet.
design discussion
low-level
potential API breaker
Windows
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
- Is
wait_overlappedthe best way to handle "call a function that takes an OVERLAPPED"? - Make
wait_overlappedreturn the information inOVERLAPPED_ENTRY, likedwNumberOfBytesTransferred - Document everything
Haven't really been thought through, need a good look over
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 reviewing the existing wait_overlapped operation and how it handles functions taking an OVERLAPPED. Clarify whether that API is appropriate, decide which OVERLAPPED_ENTRY information should be returned, and document the resulting low-level IOCP behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100