-
-
Notifications
You must be signed in to change notification settings - Fork 999
Introduce new SSLContext API & escalate deprecations.
#3319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I have updated the urllib3 transport from the gist, and it seems ready to use as well as a good example of how transport can be implemented. I've also worked a bit on AiohttpTransport, and hopefully, we'll see it soon. We could emphasize the possibility of using httpx as a Sans-IO library, capable of working with HTTP streams. |
Co-authored-by: Tom Christie <[email protected]> Co-authored-by: T-256 <[email protected]>
Co-authored-by: T-256 <[email protected]>
|
Would be very excited to see built-in websocket support on the roadmap! |
|
I'm reviewing this and thinking we ought to be aiming for an interim 0.28 release here...
|
|
Since we're now deprecating rather than removing |
Co-authored-by: T-256 <[email protected]>
SSLContext API & escalate deprecations.
Co-authored-by: Kar Petrosyan <[email protected]> Co-authored-by: T-256 <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]>
Branch for Version 1.0, so that we can incrementally merge ongoing changes and figure out at what point we want to cut a release.
NetworkOptions.proxiesescalated into removal.appescalated into removal.raw_urlinterface.Possible roadmap items...
auth,proxy&timeout.default_encoding.params,headers&cookies.content,data,files....