Event loop integration

Open
#1,088 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter, python
Domain
backend

Research direction

Start by reading PR #1079 and the event-loop integration documentation linked in the issue, including the use of kernel.do_one_iteration(). Compare that host-managed approach with Trio’s guest mode as described in the linked reference. Done would require a clearly defined integration design and agreement on how the AnyIO transition should proceed.

Written by the indexing model from the issue text.

Description

This issue is mostly for me to understand how we can move forward with the switch to AnyIO with regards to event loop integration.
It looks like this is currently done manually by the host event loop, which must call kernel.do_one_iteration() regularly.
I am wondering if we could use something like Trio's guest mode instead. There would be no need to worry about low-level details and manually run ipykernel's event loop.

cc @Carreau

Dominant language
Python
Stars
734
Forks
411
Avg merge
1d 2h
Merged PRs (30d)
9

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.

More from ipython/ipykernel

All issues in ipython/ipykernel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.