potiuk edited a comment on issue #13636:
URL: https://github.com/apache/airflow/issues/13636#issuecomment-758780708
My guess is that probably you installed airflow in `--editable` mode from
sources (pip install -e ".") and this caused 'provider' packages to be
installed as well as providers available from sources (or you have airflow
sources in the path). That confuses providers manager when combined with
PYTHONPATH pointing to airflow sources (adn might behave differently depending
on the working directory you are in). .
There are several ways of solving the problem:
1) First of all this is bad idea if you want to run in production. I
recommend to install airflow from package rather than from sources if possible.
2) If you sill decide to use --editable mode, you can uninstall all
providers (after removing all provider packages (`pip freeze | grep
'apache-airlfow-providers' | xargs pip uninstall -y` should do that ). That
should fix the problem.
3) When you install Airflow 2.0.0 you can set
`INSTALL_PROVIDERS_FROM_SOURCES` to `true` to avoid installing provider
packages in the first place
4) In Airflow 2.0.1 this will be fixed - #13439 , the providers will be
automatically removed if you install airflow in editable mode.
I am closing this now, please let me know if my diagnosis if correct and if
you managed to solve the problem.
If this is not the case, You might also have a problem that airflow is
installed in a different namespace - please let me know more details of your
installaton - how you installed airflow, which extras, whether you installed
providers, do you have backport providers installed etc. I will reopen it in
case we can find a reproducible way of getting there.
----------------------------------------------------------------
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]
