Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

commons - the main idea and usage for import #21

Open
TheML9I opened this issue Sep 11, 2020 · 0 comments
Open

commons - the main idea and usage for import #21

TheML9I opened this issue Sep 11, 2020 · 0 comments

Comments

@TheML9I
Copy link

TheML9I commented Sep 11, 2020

Hi.

Could please someone explain what was the idea of commons folder usage? Properly, I mean how to import?.

Airflow has the init func prepare_syspath() that ensures that certain subfolders of AIRFLOW_HOME are on the classpath.
That allows to import modules from folders like DAGS_FOLDER/third_party, PLUGINS_FOLDER/third_party.

For instance i have the next structure:
── module /
│ ├── commons
│ └── dags

What have to be specified for DAGS_FOLDER to be able to import modules from commons into DAG-files.
Do I have to extend sys.path manually? If I keep this by default I will get a module import error.

I'd like to make it clear how to import modules from commons folders. Why commons dirs are on that project's structure level?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant