MagicStack / MagicStack/asyncpg
Use anyio instead of asyncio for trio compatibility
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend-api-design, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100