turbaszek commented on pull request #12511:
URL: https://github.com/apache/airflow/pull/12511#issuecomment-733158598


   After discussion with @potiuk we decided to move the check to ci image. And 
that's are the problem we have:
   ```
   ➜ docker run --rm --entrypoint /bin/bash apache/airflow:master-python3.6-ci 
-c "pip check"
   snowflake-connector-python 2.2.10 has requirement 
azure-storage-blob<13.0.0,>=12.0.0; python_version >= "3.5.2", but you have 
azure-storage-blob 2.1.0.
   snowflake-connector-python 2.2.10 has requirement 
cryptography<3.0.0,>=2.5.0, but you have cryptography 3.0.
   snowflake-connector-python 2.2.10 has requirement idna<2.10, but you have 
idna 2.10.
   snowflake-connector-python 2.2.10 has requirement requests<2.24.0, but you 
have requests 2.24.0.
   moto 1.3.14 has requirement idna<2.9,>=2.5, but you have idna 2.10.
   cfn-lint 0.35.0 has requirement importlib-resources~=1.4; python_version < 
"3.7" and python_version != "3.4", but you have importlib-resources 3.0.0.
   botocore 1.17.44 has requirement docutils<0.16,>=0.10, but you have docutils 
0.16.
   astroid 2.4.2 has requirement lazy-object-proxy==1.4.*, but you have 
lazy-object-proxy 1.5.1.
   ```
   The main problem is snowflake due to 
https://github.com/snowflakedb/snowflake-connector-python/issues/324 and this 
comment:
   
https://github.com/apache/airflow/blob/ce919912b7ead388c0a99f4254e551ae3385ff50/setup.py#L385-L392
   
   what's more this library has constraint for boto3, `'boto3>=1.4.4,<1.16'`
   
https://github.com/snowflakedb/snowflake-connector-python/blob/29ad620f7d8bb14f2bb0bc1d95b4dc35b65447bb/setup.py#L195
   
   I'm wondering how we should solve it. Or what should be our criteria when 
selecting versions? 
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to