potiuk commented on pull request #12082: URL: https://github.com/apache/airflow/pull/12082#issuecomment-722383613
> Moving to dev/ is a better plan anyway, but this diff: > > https://github.com/apache/airflow/pull/10806/files#diff-> # We need to make sure we are not in the airflow checkout, otherwise it will automatically be added to the > # import path > cd / > python3 /import_all_provider_classes.py > ``` > > was how I handled this before -- that cd won't be needed anymore either I don't think. Unfotutnately, we still have to do something like that. Currently Airlfow imports settings (and probably some other stuff after that when you import "airflow" folder and if it happens to find "airflow/__init__.py" in the current working directory and no settings there, it will fail during the import. In our cae we need to have a mixture of installed version and sources in the same container (for example we need to install "all" extras from airflow 2.0 in order to test importability of all backport providers (as some of the are optional - for example apache_beam), and it will not work if we do not have the sources (or parts of it at the least). ---------------------------------------------------------------- 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]
