I think it's not too late - it depends on our assessment (guess or maybe some of our airflow-as-a-sevice stakeholders can do some statistical analysis in their user's codebase) whether those are frequently used or not.
I think it is OK to deprecate stuff in 2.11 as long as we asses that low percentage of dag files will have to be updated and that the update/replacement is trivial and can be automated with ruff. The only reason we had hard time with deprecating Jinja templates for example was that the assessment was that it affect very high percentage of DAGs and that it was not as easy and 100% accurately to convert the DAGs automatically. So if we are able to assess that and automate fix with ruff, I'd say all is open. J. czw., 5 gru 2024, 07:25 użytkownik Tzu-ping Chung <t...@astronomer.io.invalid> napisał: > We already removed those entries in the deprecated section as a part of > AIP-83. Those are also planned in the Ruff migration rule so people should > be notified if they use them in a PythonOperator (including @task). > > There are actually some other template variables I feel we should remove > (ds and ts, for example). It’s probably too late now since they are not > deprecated, but I’d be extremely happy if we could remove them. > > TP > > > > On 2 Dec 2024, at 04:07, Jens Scheffler <j_scheff...@gmx.de.INVALID> > wrote: > > > > I know, it might be a bit late but still... While cleaning deprecations > > I stumbled over deprecated context entries. > > > > We have documented these entries since 2.0 and still carry them around > > many places in the code. Just wanted to briefly drop this discussion to > > feel the temperature before VOTE. > > > > Does something as argument speaks against removing the (long time) > > deprecated context variables in Airflow 3? > > > > Who does not remember: The deprecated ones are > > > https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html#deprecated-variables > > (or search for AirflowContextDeprecationWarning) > > > > Jens > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > For additional commands, e-mail: dev-h...@airflow.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
