But it's not feature complete if it can't make modern networking requests when the whole point of a library like requests is to make networking requests.

If you can get the content of a web page using requests, then it works just fine.

> whole point of a library like requests is to make networking requests.

The whole point of requests is to make HTTP requests easy. HTTPLib was/is an arse to use.

as HTTP3 is really not that widely adopted, and where it is, has fallbacks to 1.1 whats the point?

Plus the people who are keen on HTTP3 also seem to be keen on async, https://github.com/aiortc/aioquic/tree/main/examples which even though it isn't seems to be overly complex and difficult to use. Contrast that to r.get(url)....

It’s an HTTP library that doesn’t support async or HTTP/2, let alone HTTP/3. It isn’t feature complete.

Besides, I was responding to this:

> The reason given for not including it in the stdlib was so it could evolve more rapidly.

Pointing out that it isn’t evolving at all is a perfectly reasonable response to that.