Comment by KaiserPro 16 hours ago Why would you want to use HTTPX2 over say requests? 5 comments KaiserPro Reply 12_throw_away 7 hours ago Async. And it comes with WSGI and ASGI transport adapters [1], which are amazing for testing/debugging with the client and server in a single process. And I personally find the httpx API is much cleaner and more composable, but ymmv.[1] https://www.python-httpx.org/advanced/transports/#wsgi-trans... deathanatos 5 hours ago Since it clearly intends to satisfy the async use case, I wish you'd've phrased this as "over aiohttp". imp0cat 13 hours ago You probably want to use pretty much anything over requests for performance reasons. oersted 15 hours ago async
12_throw_away 7 hours ago Async. And it comes with WSGI and ASGI transport adapters [1], which are amazing for testing/debugging with the client and server in a single process. And I personally find the httpx API is much cleaner and more composable, but ymmv.[1] https://www.python-httpx.org/advanced/transports/#wsgi-trans...
deathanatos 5 hours ago Since it clearly intends to satisfy the async use case, I wish you'd've phrased this as "over aiohttp".
imp0cat 13 hours ago You probably want to use pretty much anything over requests for performance reasons.
Async. And it comes with WSGI and ASGI transport adapters [1], which are amazing for testing/debugging with the client and server in a single process. And I personally find the httpx API is much cleaner and more composable, but ymmv.
[1] https://www.python-httpx.org/advanced/transports/#wsgi-trans...
Since it clearly intends to satisfy the async use case, I wish you'd've phrased this as "over aiohttp".
You probably want to use pretty much anything over requests for performance reasons.
async