snowflake-connector-python: Error on 2.0.3: ssl_wrap_socket_with_ocsp() got an unexpected keyword argument 'key_password'
Please answer these questions before submitting your issue. Thanks!
-
What version of Python are you using (
python --version)? 3.7.2 -
What operating system and processor architecture are you using (
python -c 'import platform; print(platform.platform())')? Mac OS X -
What are the component versions in the environment (
pip list)? https://termbin.com/28i3 -
What did you do? If possible, provide a recipe for reproducing the error. A complete runnable program is good. Install dbt with 0.10.3 and snowflake-python-connect 2.0.3.
dbt debugon any dbt project that uses snowflake and it will show
ssl_wrap_socket_with_ocsp() got an unexpected keyword argument ‘key_password’
-
What did you expect to see? No error
-
What did you see instead?’ ssl_wrap_socket_with_ocsp() got an unexpected keyword argument ‘key_password’
-
Can you set logging to DEBUG and collect the logs?
import logging
import os
for logger_name in ['snowflake.sqlalchemy', 'snowflake.connector', 'botocore']:
logger = logging.getLogger(logger_name)
logger.setLevel(logging.DEBUG)
ch = logging.StreamHandler()
ch.setLevel(logging.DEBUG)
ch.setFormatter(logging.Formatter('%(asctime)s - %(threadName)s %(filename)s:%(lineno)d - %(funcName)s() - %(levelname)s - %(message)s'))
logger.addHandler(ch)
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 27 (9 by maintainers)
Hi, why was this closed?
We can’t pin requests just to accommodate
snowflake-connector-python, and thus we’re now broken on latest.We also noticed that 1.9.0 was removed from PyPI without any notice, yet is still listed in the release notes. This broke our build process and forced us to upgrade. It’s considered extremely dangerous to remove packages after they’ve been published, and the lack of transparency is even more unsettling.
This is extremely unprofessional for a product used in production.
I have fixed the issue with the newest
urllib3and will be pinning it much less aggressively for the next release.That’s simply not enough. You need to update the PyPI page. You need to declare that it was removed, and you need to describe why. It’s unacceptable.
Last working version we had was 1.9.0 and you broke us when you removed it. Every version since then was broken with the Azure BlockBlobService error, which is only resolved with newest version
2.0.3, which then has an absurdurllib3requirement, which requires us to downgraderequests.It’s a library. It is not appropriate to lock your transitive dependencies.
Incorrect.
We’re awaiting a version that is compatible with the latest version of requests.
While waiting for 2.0.5, I’ve resorted to the following requirements when running in a lambda.
@keller00
Libraries can inform minimum constraints, but should generally not enforce maximums, leaving it up to the system administrator to lock versions if the library ends up not being compatible.
I’m hoping this is what you mean by “pinning it much less aggressively” 😃
Thanks for the update!
I didn’t change urllib. Just pinned these 2 versions.
azure-storage-blob==2.1.0 snowflake-connector-python==2.0.2
Let’s hope it’s fixed. I wasted a good hour yesterday trying to figure out why my Lambda stopped working only to find this issue and roll back the urllib3 version that adding the S3 connector lib had changed.
ok, we’ll update the doc and attempt to support the latest urllib3 and requests.
Decided to skip 2.0.5 and release 2.1.0 in the first week of December.
The 2.0.4 patched for workaround. More complete solution would be in 2.0.5
Attached recently.
v2.0.5 will have the doc update.
Can you please elaborate this? We are not aware of py3 specific issue. The above one doesn’t sound like Py3 specific but both py2 and py3.