-
-
Notifications
You must be signed in to change notification settings - Fork 844
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
Introduce new SSLContext
API & escalate deprecations.
#3319
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 <tom@tomchristie.com> Co-authored-by: T-256 <132141463+T-256@users.noreply.github.com>
Co-authored-by: T-256 <132141463+T-256@users.noreply.github.com>
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 <132141463+T-256@users.noreply.github.com>
SSLContext
API & escalate deprecations.
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
.proxies
escalated into removal.app
escalated into removal.raw_url
interface.Possible roadmap items...
auth
,proxy
&timeout
.default_encoding
.params
,headers
&cookies
.content
,data
,files
....