Replies: 2 comments 2 replies
-
Ah, I think I now see the subtlety: hyper (the client) is abandoned, but hyper-h2 (https://github.com/python-hyper/hyper-h2), which is a "pure-Python HTTP/2 protocol stack", is not. Perhaps it'd be clearer if h2 was brought under this project umbrella. As it stands, it inherits the hyper branding, which can mislead us to the dead repo (client). |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Apteryks I'll conver this to a discussion, if that's OK. :-) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Hello; that's perhaps a misunderstanding on my part, but FWIU this project absorbed hyper (h2) and had it deprecated. Yet httpx's setup.py still references to h2 (version 3!) as an extra dependency (
httpx/setup.py
Line 65 in 0f280af
What is is useful for? Can it simply be removed? What about hyper compatibility feature with requests (HTTP20Adapter) ? Is there something like this in HTTPX? Thank you, and sorry for all the questions :-).
Beta Was this translation helpful? Give feedback.
All reactions