-
Notifications
You must be signed in to change notification settings - Fork 42
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
ssl_options is broken on Python3.12 #284
Comments
@avelanarius @Lorak-mmk, are we planning syncing with upstream 3.29.0, any time soon ? or we'll need to backport the fix for this one manually ? |
Is this issue urgent to fix? I'd rather plan syncing with upstream to the next sprint (~start of February) since we already have a lot of stuff planned around Rust Driver. |
I can't tell exactly who is using ssl_options, but if they gonna move into python 3.12, it would stop working... I've hit it in dtest in few tests, that wasn't using I've fixed the dtest to stop using it, so I can move to python 3.12 |
at least scylla tests are using only |
SCT python driver is using ssl_options when create session and should be switching to use ssl_context since ssl_options is deprecated (and also broken for scylla-driver==3.26.4 ontop python 3.12) Refs: scylladb/python-driver#284
SCT python driver is using ssl_options when create session and should be switching to use ssl_context since ssl_options is deprecated (and also broken for scylla-driver==3.26.4 ontop python 3.12) Refs: scylladb/python-driver#284
SCT python driver is using ssl_options when create session and should be switching to use ssl_context since ssl_options is deprecated (and also broken for scylla-driver==3.26.4 ontop python 3.12) Refs: scylladb/python-driver#284
SCT python driver is using ssl_options when create session and should be switching to use ssl_context since ssl_options is deprecated (and also broken for scylla-driver==3.26.4 ontop python 3.12) Refs: scylladb/python-driver#284 (cherry picked from commit 62df88f)
This older style of no using ssl context, is broken on 3.26.4
Seems like it's was mostly addressed already in up stream:
datastax#1191
Maybe we should deprecated completely at our end ?
Or just sync with 3.29.0 to get it ?
The text was updated successfully, but these errors were encountered: