hmm good point maybe a good opportunity

[pine elk]

I used httpx before, simply because it’s async. Is there any other reaso to prefer it?

[marsh ridge]

Built-in types

[nocturne skiff]

its complete protocol implementation is much more flexible and better than requests

well, i wish the http parser o the time had been restkit

back before requests marketet itself as good, it was a actually good and insanely well factored http client, just lacking people working on it, then kenneth came along and made requests on top of realy bad libs but marketed it well

and now we have requests, which will necer recover from the initial bad choices, and new contenders that implement the modern protocols aready (like httpx)

</rant>

[pine elk]

Thanks! I never got into the internals of HTTP enough to be able to really compare libs.

[nocturne skiff]

requests should never have happened ^^

unfortunately it did, and now its everywhere

[pine elk]

It happened because the basic abstractions feel so elegant. resp = requests.get(url), but when you need it, you can use a session and cookies, …

If something else was that elegant at that time, people could have lobbied for that.

[nocturne skiff]

Restkit was almost there and had vastly superior internals

[pine elk]

Maybe would have been better for Kenneth to not enter the spotlight.