Oh cool, hiya! 👋

but don't really know what's involved

Implementing a concurrency backend requires implementing the AsyncBackend interface... https://github.com/encode/httpcore/blob/master/httpcore/_backends/base.py

That provides the bare bones for "give me a semaphore", "give me a lock", and "open a TCP stream", which is everything the backend needs to provide.

The asyncio and trio implementations are worth a quick look over, as the two existing async examples. (There's an equivalent sync implementation too.)

Once there's an implementation, the other bit is to tie it in with the concurrency autodetection... https://github.com/encode/httpcore/blob/master/httpcore/_backends/auto.py#L17-L28

For the tests I think it'd be a case of adding curio to https://github.com/encode/httpcore/blob/master/tests/conftest.py#L15-L20 in order to include it in the test parameterization, but I don't recall off the top of my head if there's more beyond that to do.

Should I just submit a drive-by pull request adding Curio support?

That'd be pretty fantastic if you're up for it.

Curio support #94

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions