[GitHub] [airflow] potiuk commented on issue #12943: Issue with Airflow 1.10.13, 2020-11-24 release

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

potiuk commented on issue #12943:
URL: https://github.com/apache/airflow/issues/12943#issuecomment-741844540


   > Have followed the issue template, just expecting response / resolution asap as we are in mid of release!
   
   I think you should post in slack (see airflow.apache.org - community page). This is a better place to ask such questions. Maybe someone with similar experience can help you. We are just in the middle of releasing Airflow 2.0 so do not expect a lot of attention from the committers. 
   
   It is generally expected that you won't be able to install some packages due to conflicts - Airflow has > 420 dependencies and it's only recently (1.10.14 which is sue tomorrow and 2.0.0rc which is due today) we managed to get consistent set of constraints for our tests (and even that excludes apache-beam for now). And if you add your own packages, you are a bit on your own there as we cannot really help with those and there is no guarantee those deps will work.
   
   In this particular case,  I have no high hopes though - it's pretty much unsolvable as you have conflicting dependencies. You cannot install protobuf protobuf==3.12.2 because you have the google libraries that require lower version. 
   
   You can always use PythonVirtualEnv operator https://airflow.apache.org/docs/apache-airflow/stable/_modules/airflow/operators/python_operator.html if you need to run particular python operation as suggested by Composer team : https://cloud.google.com/composer/docs/how-to/using/installing-python-dependencies
   
   


----------------------------------------------------------------
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