Jarek Potiuk
Jarek Potiuk
Let's just exclude `airflow.__init__.py` from automatically adding `from __future__ import annotations` and convert it back to use "regular" typing. We've done that for Pydantic classes before and still doing it...
I added alternative implementation - and it seems to work for me https://github.com/apache/airflow/pull/43173 - just by removing `from future` and adding ignore rules from ruff seem to do the job...
Closing this one. It's already fixed.
Comment from a side/user: agree with @notatallshaw. The worst that could happen is that users who are sticking with 3.8 will not be able to run 25.*. Which might incentivise...
BTW. My proposal above means adding support / code to produce such message in the latest version of 24.*. of course.
Would it be possible to post here when a candidate/beta is ready for testing ? I will be happy to run our extensive checks on 24.3 in Airflow - while...
> @potiuk we won't make a beta for 24.3, but you can test with the `main` branch, as it will become 24.3 later this week end. Will do and report...
Running here: https://github.com/apache/airflow/pull/43395 -> I will likely have to do small modifications, but eventually I will turn it into one-switch-testing for the future.
Update: looks good so far :)
Very interesting discussion - I was following closely, and the last few comments gave me a pause and I think I have my own comment finally :) Yep, I think...