Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTPX2 – A next-generation HTTP client for Python

github.com

Post reply on HN
Print view View original

31–40 of 50 posts

Re: HTTPX2 – A next-generation HTTP client for Python

#31

Post by niltecedu »

t098i3 wrote: post #12
BoumTAC wrote: post #11

Noob question: what's the purpose of having so many request libraries? In JavaScript it's crazy, but in Python it's starting to feel the same: requests, httpx, httpx2... From my perspective, HTTP requests have been mastered for years (decades?). What's the point of switching libraries? What's so extraordinary about the new HTTP library that makes requests look crap? I understand that new protocols appear from time to…

`requests` has a friendlier API than the standard library. However, it does not support newer versions of HTTP, nor does it support `async`. The maintainer considers it complete, feature-frozen software, IIRC - they'd rather keep it stable for existing users and let other libraries succeed it. `aiohttp` supports `async` but was never popular for non-async `httpx` supported newer HTTP versions and both async and non-a…

Also niquests as well which is a dropin replacement and imo wayyy better than httpx

Re: HTTPX2 – A next-generation HTTP client for Python

#33

Post by JackSlateur »

niltecedu wrote: post #31
t098i3 wrote: post #12

Earlier quoted context omitted.

`requests` has a friendlier API than the standard library. However, it does not support newer versions of HTTP, nor does it support `async`. The maintainer considers it complete, feature-frozen software, IIRC - they'd rather keep it stable for existing users and let other libraries succeed it. `aiohttp` supports `async` but was never popular for non-async `httpx` supported newer HTTP versions and both async and non-a…

Also niquests as well which is a dropin replacement and imo wayyy better than httpx

niquest is something like a one-man-show, which is an issue-per-se

Of course, it is clearly superior to everything else (being authored by a french guy !). But sadly, some people do not accept this simple fact :(

Re: HTTPX2 – A next-generation HTTP client for Python

#34

Post by Lindby »

jenders wrote: post #3

I would been pleased to see this project named something else, maybe “httpx-ng” or “httpy” as I immediately link “http*2” with the obsolete http/2 protocol and not the httpx project.

There is already a popular project called httpie, so httpy would be really confusing in non written form. Beside that, i completely agree, the name could be better.

https://httpie.io/

Re: HTTPX2 – A next-generation HTTP client for Python

#35

Post by giov4 »

t098i3 wrote: post #12
BoumTAC wrote: post #11

Noob question: what's the purpose of having so many request libraries? In JavaScript it's crazy, but in Python it's starting to feel the same: requests, httpx, httpx2... From my perspective, HTTP requests have been mastered for years (decades?). What's the point of switching libraries? What's so extraordinary about the new HTTP library that makes requests look crap? I understand that new protocols appear from time to…

`requests` has a friendlier API than the standard library. However, it does not support newer versions of HTTP, nor does it support `async`. The maintainer considers it complete, feature-frozen software, IIRC - they'd rather keep it stable for existing users and let other libraries succeed it. `aiohttp` supports `async` but was never popular for non-async `httpx` supported newer HTTP versions and both async and non-a…

thanks for the summary.

>`httpx` supported newer HTTP versions and both async and non-async. However the maintainer decided to close all outside submissions, issues and discussions for personal reasons.

how can something like this happen? and which positive consequence there can be out of that?

Re: HTTPX2 – A next-generation HTTP client for Python

#37

Post by fmajid »

JackSlateur wrote: post #33
niltecedu wrote: post #31

Earlier quoted context omitted.

Also niquests as well which is a dropin replacement and imo wayyy better than httpx

niquest is something like a one-man-show, which is an issue-per-se Of course, it is clearly superior to everything else (being authored by a french guy !). But sadly, some people do not accept this simple fact :(

“Niquer” means “to f*ck” in French slang

Re: HTTPX2 – A next-generation HTTP client for Python

#39

Post by t098i3 »

giov4 wrote: post #35
t098i3 wrote: post #12

Earlier quoted context omitted.

`requests` has a friendlier API than the standard library. However, it does not support newer versions of HTTP, nor does it support `async`. The maintainer considers it complete, feature-frozen software, IIRC - they'd rather keep it stable for existing users and let other libraries succeed it. `aiohttp` supports `async` but was never popular for non-async `httpx` supported newer HTTP versions and both async and non-a…

thanks for the summary. >`httpx` supported newer HTTP versions and both async and non-async. However the maintainer decided to close all outside submissions, issues and discussions for personal reasons. how can something like this happen? and which positive consequence there can be out of that?

> how can something like this happen?

https://xkcd.com/2347

Specifically in this case, the consensus seems to be the maintainer is having some mental health struggles and chose to close out outside contribution.

Re: HTTPX2 – A next-generation HTTP client for Python

#40

Post by t098i3 »

ranger_danger wrote: post #17
casper14 wrote: post #4

People should be aware how much worse HTTPX performs versus Aiohttp. For high scale systems it makes a massive difference

I searched and searched for way too long and could not find any information on whether or not aiohttp supports HTTP/2 or 3... do you know or have any reference that explains what all is supported?

It does not: https://github.com/aio-libs/aiohttp/issues/5999
Post reply on HN