ipython / ipython/ipykernel

Removing `@register_integration("asyncio")` and `def loop_asyncio(kernel):`

Open
#1,532 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
734
Forks
412
Avg merge
1d 5h
Merged PRs (30d)
8

Description

In current versions of ipykernel, when you execute in jupyter, vscode jupyter,
```
%gui asyncio
```
then after a while, when you execute
```
import asyncio
asyncio.all_tasks()```
```
you will get and see like
```
{.run_in_context() running at D:\test\ipykernel\ipykernel\utils.py:60> wait_for= cb=[Task.task_wakeup()]> cb=[ZMQStream._run_callback.._log_error() at e:\.pixi\envs\default\Lib\site-packages\zmq\eventloop\zmqstream.py:563]>,
cb=[Task.task_wakeup()]>}
```
It keeps increasing task count and it wastes your some cpu resource in the background. It's acually running these below codes, it just enters the function the return repeatedly, by `self.io_loop.call_later(0.001, advance_eventloop)` of `enter_eventloop()` in `kernelbase.py`.
https://github.com/ipython/ipykernel/blob/8816d024bf730e9fdb051b44ab2fc1ee2276cea2/ipykernel/eventloops.py#L430-L473

How it happened:
The `@register_integration("asyncio")` and `def loop_asyncio(kernel):` was at the old ages, to drive the asyncio codes that inputed by users, like `asyncio.ensure_future(...)`, when ipykernel was running under `IOloop` of `tornado<6.1` which using the `selectorloop` or even older type eventloop. It was to make users able to run asyncio codes when the underhood is other things.
The current ipykernel its main loop is already asyncio loop, by `IOloop` of `tornado>6.1`. The user inputed asyncio codes already run in the main loop.

Therefore the related codes `@register_integration("asyncio")` and `def loop_asyncio(kernel):` could be deleted.

Solution:
related issue: https://github.com/ipython/ipykernel/pull/1469 solving the proactor and selector eventloop within asyncio

Contributor guide

Open the contributing guide

Research direction

Start with ipykernel/eventloops.py around the linked integration code and trace how it is invoked from enter_eventloop() in kernelbase.py. Compare the behavior with the asyncio event-loop changes described in pull request 1469, then verify that repeated %gui asyncio execution no longer causes the asyncio task count to grow or wastes CPU.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
66/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.