100%. It’s on my list to tackle very soon, it can’t get put off much longer.
I have some thoughts (around back compat mostly) but they aren’t collected yet, and I won’t derail this thread. > On 15 Feb 2025, at 21:43, Jarek Potiuk <ja...@potiuk.com> wrote: > > cc: @ashb @uranusjr @kaxil -> something for consideration in our > discussions on how to repackage airlfow soon. I keep on explaining why > running code in airflow.__init__.py is a bad idea and advocating for > removal of it and replace it with explicit initialization, yet that topic > have not been discussed yet, but I will plan to start a discussion about it > soon once we approach the packaging subject. I am not sure what's your > thinking is about this - I know you spent consirderable amount of time on > doing all the "lazy initalization" dance all over the places, and I think > it adds a lot of complexity to our code and only partially solves the > cicular imports problem. But I know @ashb has very strong feeling about > being able to do "from airlfow import Dag" - which more or less requires > all this complexity. I just don't think it's worth it.
