Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Use anyio instead of asyncio for trio compatibility

Open
#1,119 0 comments 16 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
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, python
Domain
backend-api-design, databases

Research direction

The issue names no files or tests. Start by mapping direct asyncio use throughout asyncpg and determining the scope of anyio and Trio compatibility; the work is complete when asyncpg no longer relies directly on asyncio for the covered paths and users can choose their preferred concurrency backend.

Written by the indexing model from the issue text.

Description

Currently, it is difficult (even with trio-asyncio) to mix asyncio-using and trio-using libraries in the same project. Replacing direct use of asyncio throughout asyncpg with anyio will allow users to choose the concurrency backend that they prefer and increase asyncpg's compatibility with other async libraries.

Dominant language
Python
Stars
8.1k
Forks
469
Avg merge
2d 20h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

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 MagicStack/asyncpg

All issues in MagicStack/asyncpg

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.