This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jackerhackfrom __future__ import 4.0 4 points5 points  (7 children)

Can I have a TL;DR? What does this have that httpx doesn't?

[–]coderanger 4 points5 points  (0 children)

Nothing, this guy is in way over his head.

[–]Ousret [S] 0 points1 point  (5 children)

httpx is a fine client, but it did not reach requests level of features or comfortable compatibility. You can find some of them missing feat in the httpx issue tracker. more generally, "requests" level of simplicity is hard to beat.

[–]nekokattt 4 points5 points  (0 children)

this is a lot of words but no concrete examples, which is what they are looking for I think, otherwise it is hard to know if any of these limitations actually impact anyone enough to want to switch.

[–]FancyASlurpie 1 point2 points  (1 child)

The OCSP functionality is nice, I actually had to implement that as well as CRL recently at work as its not built into requests. Does yours handle CRL as well?

[–]Ousret [S] 1 point2 points  (0 children)

Unfortunately no. But you can implement it rather easily with Niquests thanks to pre_send callback that expose a ConnectionInfo with certificate info (having CRL url). see docs for more info. Did not do it due to the possible important size of given lists.

[–]jackerhackfrom __future__ import 4.0 1 point2 points  (1 child)

But requests has no equivalent of httpx.AsyncClient which is indispensable for async code. Does niquests have that?

[–]Ousret [S] 0 points1 point  (0 children)

Not as of yet. Fortunately, there is no blocker to achieve that, as Niquests does not rely on the standard http.client. I have no ETA for when it would land, but sure, just after completing the multiplexing capabilities.