Boto3 does not work with openssl 2.x #3490
-
Describe the bugHello, The Databricks runtime 10.5 introduced an upgrade of openssl from 1.4.6 to 2.0.0, after that change, the latest boto3 library fails to install:
TypeError: deprecated() got an unexpected keyword argument 'name' On databricks runtime 10.4 everything works just fine. Could you please remove the deprecation issue? Thank you! Best regards, Expected Behaviorpip install boto3 pass Current Behaviorpip install boto3 on databricks 10.5+ fails Reproduction StepsOpen any databricks platform run a pip install boto3 on that platform. Possible SolutionUpgrade openssl depedency Additional Information/ContextNo response SDK version usedlatest release Environment details (OS name and version, etc.)databricks 10.5 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi @azachar thanks for reaching out. I think the error is due to using pyOpenSSL and boto3 in the same environment. There was a recent issue (boto/botocore#2744) that goes into more detail about the incompatibilities and deprecation. |
Beta Was this translation helpful? Give feedback.
-
Ran into this and I'm not 100% sure how I fixed it but hoping this might help someone searching for keywords (as I was):
There's a mix of I removed everything in my system 😅 (be careful with this, but really, things should be
After reinstalling my package (which uses boto3 as a dependency) I did TL;DR I think if you have pyOpenSSL that's bad and unnecessary (according to the linked GH thread). |
Beta Was this translation helpful? Give feedback.
-
I'm converting this issue to a Discussion rather than a bug because the problem involves pyOpenSSL and this is something that can't be controlled from the boto3 side. For more background please refer to the issue linked earlier. Removing pyOpenSSL as mentioned above should fix the issue. |
Beta Was this translation helpful? Give feedback.
I'm converting this issue to a Discussion rather than a bug because the problem involves pyOpenSSL and this is something that can't be controlled from the boto3 side. For more background please refer to the issue linked earlier. Removing pyOpenSSL as mentioned above should fix the issue.