python-trio / python-trio/trio

Improve low-level IO monitor functions (for IOCP and kqueue)

Open
#40 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

low-level potential API breaker todo soon
Dominant language
Python
Stars
7.3k
Forks
431
Avg merge
2d 17h
Merged PRs (30d)
6

Description

These should take a queue, rather than returning a queue, to support the case where you want to register multiple filters and multiplex them onto the same queue. (This is probably more important for kqueue than IOCP, b/c in IOCP you can take the completion key and use it for multiple registrations? but either way.)

CompletionKeyEventInfo should also carry the actual completion key, b/c it becomes ambiguous.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the low-level IO monitor functions for IOCP and kqueue, along with CompletionKeyEventInfo. Trace how queues and completion keys are currently passed and represented. Done means multiple filters can share a supplied queue and CompletionKeyEventInfo carries the actual completion key.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.