potiuk edited a comment on pull request #11526: URL: https://github.com/apache/airflow/pull/11526#issuecomment-709323347
> I _think_ we can get away without any Would love to hear how :). I thought the same, but I am not so sure any more. I actually tested it and if you do `pip install .` now, the providers are not installed and if you are not in the "airflow" folder (, in pyhton 3.6+ is by default on python path) you won't be able to import providers. Also when we add dependencies in extras, as you will see now - if you try to install airflow[google] - it will fail now because it won't find the apache-airflow-google-package. So I wonder how you would like to avoid those two problems. We can of course do a "proper" sub-provider setup.py and keep separate setup.py per provider and split it and then have dependent package structure from airflow, but that would be a lot of maintenance, and especially if you want to manage common set of dependencies for the whole airflow, that woudl be quite complex. But If you would like to solve that this way - feel free :). ---------------------------------------------------------------- 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]
