`_eventloop_set` event called from non-async context

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading ipykernel/kernelbase.py at the referenced line and review pull requests 1265 and 1291 for how _eventloop_set was introduced and exposed on a Trio backend. Reproduce the failure in a non-async context, then verify that the event can be handled safely there without breaking the existing async behavior.

Written by the indexing model from the issue text.

Description

The _eventloop_set AnyIO event cannot be set here, because it may be called from a non-async context. This event was introduced in https://github.com/ipython/ipykernel/pull/1265 and the issue was revealed in https://github.com/ipython/ipykernel/pull/1291 when running on a trio backend.

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.