Congratulations Rahul 🎊
On Tue, 1 Apr, 2025, 08:56 Aritra Basu, wrote:
> Congrats Rahul, great job!
> --
> Regards,
> Aritra Basu
>
> On Tue, 1 Apr 2025, 8:42 am kalyan reddy, wrote:
>
> > Congratulations Rahul! Thanks for your amazing work. Well deserved !!
> >
Hi All,
I’m excited to announce that the *Sequential Executor* and *Debug Executor*
have been removed from the in-tree executors in our repository, thanks to
the efforts of the community! (Discussed in
https://lists.apache.org/thread/65jw3o3mn7qlc56f9bt2146fmoy0z5t6).
These executors were primari
We were going to have compatibility shims to redirect the imports - with -
there are few ways to do it - Ash had a little POC with module loader, but
I think it has some potential side effect and I think Ash abandoned
the idea and I would personally prefer to use our old PEP-563 mechanism
using air
An example where deprection_tools are still used
https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/utils/log/__init__.py
It's rather straightforward = needs a package with __init__.py - only where
you list all the classes and provide redirections. It will
automatically raise dep
Those were deprecated 4.5+ years ago:
https://github.com/apache/airflow/blob/2.0.0/airflow/operators/python_operator.py
On Tue, 1 Apr 2025 at 21:45, Kaxil Naik wrote:
> Instead handle it via ruff rules AIR2 something
>
> On Tue, 1 Apr 2025 at 21:44, Kaxil Naik wrote:
>
>> ` - ModuleNotFoundErr
Ah.. I missed that we have those _operators ... Those indeed should have
been fixed a long time ago and automated conversion rules from ruff
should be fixing them.
On Tue, Apr 1, 2025 at 6:17 PM Kaxil Naik wrote:
> Those were deprecated 4.5+ years ago:
>
> https://github.com/apache/airflow/blob/
+1 binding. Checked signatures, checksums, licences, reproducibility - all
good. All my changes are in (updated images mostly), installed and run
airflow and 2.10.5 was up-and-running flawlessly. All good to go.
On Tue, Apr 1, 2025 at 7:41 AM Amogh Desai wrote:
> +1 non binding.
>
> I didn't hav
Hello all,
The vote to release Apache Airflow Helm Chart version 1.0.1 based on
1.0.1rc1 is now closed.
The vote PASSED with 3 binding "+1", 2 non-binding "+1" and 0 "-1" votes:
"+1" Binding votes:
- Jed Cunningham
- Jens Scheffler
- Jarek Potiuk
"+1" Non-Binding votes:
- Vishnu Chilu
Hi Kaxil,
> Instead handle it via ruff rules AIR2 something
Does that mean we need to add an `AIR2` for `_operator`? In the current
implementation, they are in `AIR303` (moved to provider).
It also raises a new thing I'd like to confirm.
We're to mark the suggested change for `airflow.operators
Dear Airflow community,
I am pleased to announce that we have released Apache Airflow Helm chart
1.16.0 🎉 🎊
The source release, as well as the "binary" Helm Chart release, are
available:
📦 Official Sources:
https://airflow.apache.org/docs/helm-chart/1.16.0/installing-helm-chart-from-sources.ht
IMHO, if they were deprecated that long ago then adding a ruff rule is just
enabling the users to ignore the deprecation. They should /eventually/ have to
clear some of their tech debt and actually update their code to modern
standards, no? They've had four and half YEARS of warning at this po
Instead handle it via ruff rules AIR2 something
On Tue, 1 Apr 2025 at 21:44, Kaxil Naik wrote:
> ` - ModuleNotFoundError: No module named
> 'airflow.operators.python_operator'` <-- those paths are Airflow 1.x old
>
> We had already stripped `_operator` from the module names in Airflow 2.0.0
>
` - ModuleNotFoundError: No module named
'airflow.operators.python_operator'` <-- those paths are Airflow 1.x old
We had already stripped `_operator` from the module names in Airflow 2.0.0
-- so IMO there is no need to keep back-compatibility for something that
was working 2 major versions ago
Congratulations Rahul, very well deserved!
On Tue, Apr 1, 2025 at 10:35 AM Karthikeyan wrote:
> Congratulations Rahul. Thanks for all your efforts towards the Airflow 3
> release including detailed bug reports that improved release stability.
>
> On Tue, Apr 1, 2025 at 12:53 PM Kunal Bhattachary
Yay! Moar deletions!
Just one comment to that - we **know** that forking + threading in MacOS
causes SEGV (Segmentation Violation) issues when you are using some
additional libraries that can get initialized by **just** importing them
and they start threads, when it happens before we attempt to ma
Hi everyone.
I am testing compatibility of Airflow 2 DAGs with Airflow 3, and would like
to discuss this topic.
I took bunch of DAGs from existing Airflow 2 instances and deployed them to
instance with Airflow 3 (3.0.0b4) and have bunch of import errors:
- ModuleNotFoundError: No module named '
Hi Eugen
As others have said
from airflow.operators.python_operator import PythonOperator
has been deprecated a long time ago and wont work anymore in Airflow 3.
from airflow.operators.python import PythonOperator
which was the preferred import for recent years is going to get deprecated
17 matches
Mail list logo
