You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working towards a simplified SSL configuration API.
For users of the standard verify=True or verify=False cases, or verify=<ssl_context> case this should require no changes. The following cases have been deprecated...
The verify argument as a string argument is now deprecated and will raise warnings.
The cert argument is now deprecated and will raise warnings.
Our revised SSL documentation covers how to implement the same behaviour with a more constrained API.
Now this code generates a deprecation warning (assuming you have verify_ssl_certs enabled, which is True by default).
DeprecationWarning: `verify=<str>` is deprecated.
Use `verify=ssl.create_default_context(cafile=...)` or
`verify=ssl.create_default_context(capath=...)` instead.
To Reproduce
Fetch any resource via the HTTPX client 🤷
Expected behavior
No warning 😄
Code snippets
No response
OS
any
Language version
3.11
Library version
stripe==11.3.0
API version
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
First of all, this is not really a bug.
The latest version of httpx (0.28) has introduced a deprecation like so:
Now this code generates a deprecation warning (assuming you have
verify_ssl_certs
enabled, which isTrue
by default).To Reproduce
Expected behavior
No warning 😄
Code snippets
No response
OS
any
Language version
3.11
Library version
stripe==11.3.0
API version
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: