For maximum compatibility with all the different setups out there, we should expose every httpx.AsyncClient constructor kwarg, so that users have more control over the HTTP(S) client.
Considerations
This, of course, makes it more difficult to switch to a different underlying HTTP(S) library under the hood, but there are no indications HTTPX will stop being maintained or superseded by a different library. So this seems like an acceptable change.
Tasks
verify(#42)For maximum compatibility with all the different setups out there, we should expose every
httpx.AsyncClientconstructor kwarg, so that users have more control over the HTTP(S) client.Considerations
This, of course, makes it more difficult to switch to a different underlying HTTP(S) library under the hood, but there are no indications HTTPX will stop being maintained or superseded by a different library. So this seems like an acceptable change.