python-async-patterns
Async Python patterns for non-blocking I/O with asyncio: TaskGroup, cancellation, timeouts, backpressure, rate limiting, and safe sync/async boundaries. Use when implementing concurrent network/DB workflows or async services — not for thread/process GIL tuning (python-performance) or general Python
v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/python-async-patternsGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotef0f17967…a761dfd9
f0f17967d51f…5977a761dfd96 arquivos · 5.6 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/AeonDave/malskill/tree/main/coding/python-async-patterns@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
This skill focuses on practical asyncio patterns for I/O-bound concurrency.
Thread/process/subinterpreter parallelism and the GIL are python-performance / python-patterns concurrency.md.
When to activate
- You’re building an async service/client (HTTP, DB, queues, websockets)
- You need concurrency with limits (rate limiting, semaphores)
- You need safe cancellation and timeouts
- You suspect event loop blocking (sync call inside async path)
- A task is stuck: 3.14+ call-graph /
python -m asyncio pstree
Rules of engagement
- Prefer async only for I/O-bound workloads.
- Never block the event loop (no
time.sleep(), no sync HTTP/DB in async code). - Make cancellation and timeouts explicit.
- Bound concurrency; unbounded
gather()can turn memory into a queue. asyncio.CancelledErroris aBaseException.except Exceptionwill not see it. Cleanup, then re-raise.- Do not call
asyncio.get_event_loop()to create work. From sync code useasyncio.run()(orasyncio.Runner3.11+). Inside async code useget_running_loop()only when you must.
Outcome expectations
- Concurrent I/O tasks are orchestrated with clear boundaries and failure semantics.
- Cancellation and timeouts are explicit and tested.
- Event loop is never blocked by sync calls; backpressure prevents unbounded growth.
Recommended workflow
- Define scope and concurrency bounds before writing async code.
- Use TaskGroup for orchestration; avoid fire-and-forget
create_task. - Apply timeouts at I/O boundaries, not broad scopes.
- Test cancellation paths; use pytest-asyncio with function-scoped loops.
- Profile event loop blocking; offload sync work via
to_thread()when necessary.
Quick patterns
Concurrent fan-out with bounds (TaskGroup preferred)
Prefer asyncio.TaskGroup (Python 3.11+) for structured concurrency with clear failure propagation.
async with asyncio.TaskGroup() as tg:
tg.create_task(fetch_url(url1))
tg.create_task(fetch_url(url2))
# All tasks joined; exceptions aggregated as ExceptionGroupFor concurrency limits, add a semaphore:
sem = asyncio.Semaphore(10)
async def bounded():
async with sem:
return await fetch_url(url)Timeouts
- Prefer
asyncio.timeout()(3.11+) for scoped timeouts. On expiry it raisesTimeoutError(builtin).asyncio.TimeoutErroris a 3.11+ alias of that builtin — preferTimeoutError. asyncio.timeout(None)means no timeout.
Cancellation
task.cancel()is not awaitable; it returnsbool(False if already done). Thenawait taskand handleCancelledError.- Catch
CancelledErroronly to clean up, then re-raise.
Sync/async boundary
- Offload truly blocking work via
asyncio.to_thread().
Resources
Load on demand:
references/foundations.md— event loop, coroutines vs tasks, TaskGroup vs gather, 3.12 eager tasks, 3.14 call graphsreferences/cancellation-timeouts.md—cancel()/CancelledError/timeout/uncancelreferences/backpressure-rate-limit.md— queues (QueueShutDown3.13+), semaphores, producer/consumer, rate limitingreferences/sync-async-interop.md—to_thread, executors, free-threaded loops (3.14)references/testing.md— pytest-asyncio and cancellation tests (pair withpython-testing)
Arquivos desta versão
references/510.8 KB
- backpressure-rate-limit.md1.3 KB
- cancellation-timeouts.md2.7 KB
- foundations.md3.6 KB
- sync-async-interop.md1.3 KB
- testing.md2.0 KB
- SKILL.md3.9 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | f0f17967 | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Rede, wireless e telecom
Ver a categoria- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login