libp2p/py-libp2p

Make py-libp2p async-library-agnostic with anyio

Open

#383 opened on Dec 17, 2019

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (238 forks)auto 404
help wanted

Repository metrics

Stars
 (618 stars)
PR merge metrics
 (PR metrics pending)

Description

Coming from https://github.com/libp2p/py-libp2p/issues/174#issuecomment-560470465, and based on some conversation with @mhchia, I'm making this issue as a reminder to eventually make the library completely io-agnostic by implimenting it with anyio, an asynchronous io abstraction library (which currently supports asyncio, trio, and curio).

This'll tie #349, #347 and #174 into one problem, while staying in async library ecosystems of all 3 (possibly 4)

Anyio documentation: https://anyio.readthedocs.io/en/latest/index.html Pypi project: https://pypi.org/project/anyio/

Contributor guide

Research direction
Study the existing asyncio usage in py libp2p and understand anyio's API to replace asyncio specific primitives with anyio equivalents. Focus on #349, #347, #174 to see related work.
Tech stack
python
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonasync/awaitanyio
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40