And relevant changes: complete the isolation work. IMHO - this is absolute prerequisite to make it happen. Happy to spend significant time on it in 3.5.0 course of development.
On Wed, Oct 28, 2026 at 12:07 PM Jarek Potiuk <[email protected]> wrote: > +10 on the goal. > > On Wed, Oct 28, 2026 at 10:40 AM Ash Berlin-Taylor <[email protected]> wrote: > >> Hi everyone, >> >> Now that 3.4 is almost here (if you haven’t yet tested the beta2 or, or >> the RC due this week, please do it!) I’d like to start a discussion and >> “requirements gathering” for something that Jarek, Kaxil and I have been >> talking about wanting to do since 3.0, namely: >> >> Make it so that `import airflow` is fast, and side-effect free. >> >> The high level idea behind this plan is that “everything” in >> apache-airflow-core will that lives under airflow-core/src/airflow/ today >> will move to to airflow-core/src/airflow/core/. >> >> - There will be no airflow/__init__.py anymore (or maybe just a >> back-compat shim somewhere) >> - Importing airflow will not automatically load settings, providers, >> plugins, initialised ORM connections, or configure logging. (The entry >> points themselves will need to explicitly call a new fn now) >> >> As I said, the main goal here is speed, especially for unit tests _of >> users_ (Airflow’s own unit tests will need to initialise in most cases I >> imagine). >> >> Does anyone else have any related (or conflicting) changes they’d like to >> see? >> >> -ash >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
