You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that almost all of HTTPX internals are relying on the concurrency backend, and before tackling the Trio backend (#120), it would be good to parametrize all tests with a backend fixture.
For now, it would only point to AsyncioBackend, but we're going to need it for TrioBackend anyway — the main goal is to reduce clutter when the trio backend lands a PR.
Once the backend fixture is defined, any test that uses AsyncClient, HTTPConnection or ConnectionPool can basically be parametrized with it, e.g.:
Now that almost all of HTTPX internals are relying on the concurrency backend, and before tackling the Trio backend (#120), it would be good to parametrize all tests with a
backend
fixture.For now, it would only point to
AsyncioBackend
, but we're going to need it forTrioBackend
anyway — the main goal is to reduce clutter when the trio backend lands a PR.Once the
backend
fixture is defined, any test that usesAsyncClient
,HTTPConnection
orConnectionPool
can basically be parametrized with it, e.g.:I'll tackle this look soon, but if anyone has thoughts on this approach let me know. :-)
The text was updated successfully, but these errors were encountered: