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

Migrating to HTTPX2

github.com

Post reply on HN
Print view View original

91–100 of 119 posts

Re: Migrating to HTTPX2

#91

Post by KaiserPro »

tankenmate wrote: post #60
KaiserPro wrote: post #54

Earlier quoted context omitted.

because its over QUIC, which is different enough to be a pain. Not that there is anything wrong with QUIC, at least its built by someone who knows what they are doing, unlike HTTP2

that's not really much of an argument, almost all reasonable libraries wrap the functionality.and if a provider doesn't want to support http3 then the library will fallback, and then the laggards should pay the slow tax.

No as in the infra between you and the end user is less developed.

Nobody is going to get fired for using http1.1

if you move to http3 and a bunch of clients cant use your site, then you're gonna get yelled at.

Re: Migrating to HTTPX2

#92

Post by jelenzelen »

simonw wrote: post #10

Anthropic made the same change a few weeks after OpenAI did: https://github.com/anthropics/anthropic-sdk-python/releases/... The problem with httpx as a dependency is that it's currently working towards a 1.0 release which will be full of breaking changes. The httpx2 project is essentially a fork that promises not to break the existing API, which makes it a more stable dependency to build against. I wrote a pretty lo…

Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784. I do not even understand what is his problem (too much or too little woke internet?).

Re: Migrating to HTTPX2

#94

Post by sirfz »

ushakov wrote: post #70

we have recently switched from httpx for the same reason but instead went with the Rust-based pyqwest (runs on Hyper) it has also a drop-in httpx-compatible transport so migration was easy and also it supports http2 trailers https://pyqwest.dev

Why not pyreqwest?

Re: Migrating to HTTPX2

#95

Post by mmerickel »

giov4 wrote: post #85
Aurornis wrote: post #32

Earlier quoted context omitted.

> The problem with httpx as a dependency is that it's currently working towards a 1.0 release which will be full of breaking changes. The httpx maintainer closed off access to issues and discussions on the repo, has been ignoring PRs, and hasn’t updated it in a half a year. I don’t think there is any reason to consider httpx as a viable project any more. The Pydantic httpx fork has taken its place.

unbelievable, how can a single person affect negatively FOSS so much? I mean really, closing repos? excluding maintainers? committing only on private repos? This type of behavior should be moderated and banned from any FOSS activity to avoid exactly this situation of becoming a liability. I've never seen a open source project page without a github link or a git clone ref like this https://www.encode.io/hx/ it is so r…

This level of entitlement is the reason that FOSS has a maintenance / support epidemic. Maintainers don't owe you anything. They put the work in, not you.

Re: Migrating to HTTPX2

#97

Post by skullone »

tosh wrote: post #2

nb: operating system TLS trust store is used now (instead of certifi)

Ugh. certifi the most annoying thing ever. It snuck into numerous python dependencies, never made anything better, and confuses all the junior devs when their venvs/containers etc can't access internal CA signed resources. Probably have explained what to do over 9,000 times. And for what? "To provide updated root CAs". Meh. I don't need daily CA trust store updates. If your CA roots are that new, I want nothing to do with it. Cert issuers (cough sectigo and their amateur hour CA root rotation recently, not even Mozilla had it).

Re: Migrating to HTTPX2

#98

Post by 12_throw_away »

KaiserPro wrote: post #55

Why would you want to use HTTPX2 over say requests?

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...

Post reply on HN