[GitHub] [airflow] potiuk edited a comment on issue #12881: Snowflake python connector monkeypatches urllib and makes many services unusable.

[GitBox <gi...@apache.org>]

potiuk edited a comment on issue #12881:
URL: https://github.com/apache/airflow/issues/12881#issuecomment-761566497


   > @potiuk that is true, however it means snowflake operators cant be reliably used right?
   
   Why? I think the dependencies that are left are pretty ok and we are also upgrading azure provider so that the last conflicts are removed. From what I see boto dependency in snowflake connector is:
   
   ```
   boto3>=1.4.4,<2.0.0
   ```
   
   
   So nothing extraodirinary -  taking into account that latest released version is 1.16.56. 
   Do you KNOW that you have some other conflicts, or do you just suspect it ?
   
   From the latest set of constraints generated for Airflow (I just merged the snowflake change and regenerated constraints) - we have those constraints 'blessed" for airflow (3.6 example):
   
   https://github.com/apache/airflow/blob/constraints-master/constraints-3.6.txt
   
   * boto3==1.15.18 (not latest but this is because amazon provider limits it (`boto3>=1.15.0,<1.16.0`) - if amazon provider is 
                                upgraded, it will go up
   * snowflake-connector-python==2.3.8 (latest)
   * requests==2.25.1 (latest)
   * urllib3==1.25.11 (not latest but it is not limited by python-snowflake-connector) - actually one of my fixes to the connector
                                which I contributed to snowflake was getting rid of the urllib3 dependency altogether as they did not need it.
                                The < 1.26 comes from boto-core actually, so if amazon provider goes up with botocore, this one will go up 
                                as well.
   
   Do you think your problems are not solved by this?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org