Migrating to HTTPX2
github.com
Migrating to HTTPX2
1–10 of 119 posts
Re: Migrating to HTTPX2
#2Re: Migrating to HTTPX2
#3But what are the upsides of this change?
Re: Migrating to HTTPX2
#4Re: Migrating to HTTPX2
#5nb: operating system TLS trust store is used now (instead of certifi)
Re: Migrating to HTTPX2
#6There seems to be a bunch of downsides mentioned... But what are the upsides of this change?
> I've closed off access to issues and discussions.
> I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value.
https://www.reddit.com/r/Python/comments/1rl5kuq/anyone_know...
Re: Migrating to HTTPX2
#7nb: operating system TLS trust store is used now (instead of certifi)
what's `nb` ?
Re: Migrating to HTTPX2
#8There seems to be a bunch of downsides mentioned... But what are the upsides of this change?
https://github.com/encode/httpx/discussions/3784 > I've closed off access to issues and discussions. > I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value. https://www.reddit.com/r/Python/comments/1rl5kuq/anyone_know...
Re: Migrating to HTTPX2
#9Re: Migrating to HTTPX2
#10The 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 long comment about my concerns for the breaking 1.0 version last year - https://github.com/encode/httpx/discussions/3344#discussionc... - in that comment I recommended the HTTPX project release their 1.0 as a package called httpx2 instead, but a year later we now have an httpx2 (released by a different maintainer) that keeps the old API.