interrupt issues with async code

Offen

#1,239 erstellt am 22.5.2024 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@Carreau arbeitet bereits daran.

Seit 26.8.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

bug

Hi,

Aside from the now fixed #881, I still run into some async + interrupt issues. I'm not 100% sure if I need to do something differently or there is a way to do what we mean.

The following is not interrupted and always run to completion. If you sleep instead of httpx.get (or request.get), it works as expected.

import asyncio
import httpx
from tqdm.asyncio import tqdm as tqdm_async

semaphore = asyncio.Semaphore(1)

x = 0
async def one_at_a_time():
    global semaphore

    async with semaphore:
        global x
        # await asyncio.sleep(1)
        httpx.get('http://httpbin.org/delay/1')
        x += 1
        print(x)
    return x

await tqdm_async.gather(*[one_at_a_time() for _ in range(10)])

Ideally, I want these to be tasks so I can cancel them. Again, interrupt has no effect:

import asyncio
from time import sleep
from tqdm.asyncio import tqdm as tqdm_async

semaphore = asyncio.Semaphore(1)
x = 0
async def one_at_a_time():
    global semaphore

    async with semaphore:
        global x
        sleep(1)
        x += 1
        print(x)
    return x

async def outer_async():
    return await one_at_a_time()
    
await tqdm_async.gather(*[asyncio.create_task(one_at_a_time()) for _ in range(10)])

Any suggestions for how to fix my code to work better with ipykernel or how to fix ipykernel (or IPython) itself? Even better would be something that works on 6.x, but I think that may be challenging as even #881 is not fixed there.

Vorherrschende Sprache: Python
Sterne: 734
Forks: 411
Ø Merge: 1 T. 6 Std.
Gemergte PRs (30 T.): 10

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ipython/ipykernel

`Kernel._control_lock` created after it may be used Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100

ipython/ipykernel#1567 · 1 Kommentar · Erstellt am 22.9.2026
pytest seems to be the testrunner - not nose, as mentioned in README Offen

Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 72/100

ipython/ipykernel#554 · Erstellt am 17.10.2020
post_execute fires during comm_msg handling on a subshell, so output published from the hook is parented to the comm_msg and dropped by frontends Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100

ipython/ipykernel#1564 · Erstellt am 21.9.2026
Shell reply sent raw on the ROUTER can drop the ZMQStream wake-up; a request arriving in that window is not read until the next connection Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 68/100

ipython/ipykernel#1554 · 1 Kommentar · Erstellt am 07.9.2026
Interrupt on swallowed `KeyboardInterrupt` exceptions (`SIGINT`) when pressing twice (within 5 seconds) Offen

ipython/ipykernel#1550 · 1 Kommentar · 1 Reaktion · 1 zugewiesene Person · Erstellt am 25.8.2026

Alle Issues in ipython/ipykernel