GitHub user hamedrabah added a comment to the discussion: [Proposal] Separate DAG discovery path from DAG bundle import root
Thanks @samraj2k — I agree that large monorepos are the strongest case for relaxing the current assumption. My remaining concern is scope, not whether the parser subprocess itself is isolated: bundle code is also reloaded for task execution and callbacks, so the import root needs to travel with the same versioned bundle checkout in every execution context.\n\nI would support the proposal with four constraints: keep import_root = path as the default; resolve it within the same initialized and versioned checkout rather than an arbitrary host path; propagate it consistently to parsing, task execution, and callbacks; and add tests for duplicate top-level module names plus cross-bundle leakage. With those semantics explicit, a dev-list thread sounds worthwhile. GitHub link: https://github.com/apache/airflow/discussions/70313#discussioncomment-18209935 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
