2.10.3 raises AttributeError: partially initialized module 'airflow' has no attribute 'utils' (most likely due to a circular import) #43971
Answered
by
potiuk
idexxbernvaug
asked this question in
Q&A
-
|
Hello! I am trying to update Airflow to 2.10.3 from 2.10.2 to resolve a Dependabot finding, but I am getting these errors when trying to run my test suite, pasted below. I am a little stumped, but maybe this is related to #43334 ? I don't get these errors on 2.10.1 or 2.10.2 Any help to get things working again would be much appreciated. I am sure there is just a setting that I have missed. I am using docker-compose with environment variables and not a conf file, and I confirmed that I am using: Please let me know what info I can provide to help arrive at a solution. |
Beta Was this translation helpful? Give feedback.
Answered by
potiuk
Dec 12, 2024
Replies: 2 comments 1 reply
-
|
I'm having this same issue. Did you find a fix for this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Try 2.10.4rc1 -> that should be fixed. There was the unconditional deprecation warning accidentally generated in 2.10.3 and you seem to have custom logger importing stuff from airflow - since that warning is generated during importing, your logger attempts to import some module from airflow while it is partially imported and it creates recursive import error. You can - possilbbly workaround it also by figuring which custom import on your side triggers it, and turn it into local import - in case it is a "top-level` import in a pytho file - this usually help. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
2.10.4rc1 works! I will probably wait for the release to actually update, but using 2.10.4rc1 instead of 2.10.3 in our testing environment works. I am not aware of any custom loggers. It's probably inherited from one of the providers. We are overriding some log levels so I guess that could be causing it too. Thanks! |
Beta Was this translation helpful? Give feedback.
Answer selected by
idexxbernvaug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Try 2.10.4rc1 -> that should be fixed. There was the unconditional deprecation warning accidentally generated in 2.10.3 and you seem to have custom logger importing stuff from airflow - since that warning is generated during importing, your logger attempts to import some module from airflow while it is partially imported and it creates recursive import error.
You can - possilbbly workaround it also by figuring which custom import on your side triggers it, and turn it into local import - in case it is a "top-level` import in a pytho file - this usually help.