We learned that, when installing the upcoming urllib3-2.0.0, it would effectively drop support for TLS 1.0 and 1.1 by default, and crate-python does not offer corresponding fallback adjustments yet. In order not to break things too sloppily, let us postpone this transition, in the spirit of "better safe than sorry".
If you still need to use TLS 1.0 or 1.1 in your application you can still upgrade to v2.0, you’ll only need to set ssl_minimum_version to the proper value to continue using legacy TLS versions.
We learned that, when installing the upcoming
urllib3-2.0.0
, it would effectively drop support for TLS 1.0 and 1.1 by default, andcrate-python
does not offer corresponding fallback adjustments yet. In order not to break things too sloppily, let us postpone this transition, in the spirit of "better safe than sorry".In order to follow up on this, I've created crate/crate-python#632.
/cc @seut