@tomchristie wrote:
Worth keeping in mind too, that there’s still lots of work going on in the async HTTP client space that you’ll want to keep your eye on.
The
requests-async
package is the minimal amount of work that was needed to get an async equivelent ofrequests
, but I’m still pushing hard towards maturing that all the way into a requests-compatible package that’s built from the ground up with either sync or async functionality, plus HTTP/2 support, a parallel requests API, test client adapter etc.etc.Best place to keep up to date with progress there is probably this issue: https://github.com/encode/httpcore/issues/78