shared document
<https://docs.google.com/document/d/1QcQaejbBgpHzAjLHyx9KNG1d1JKdYkWjhrR6XzZ_0tE/edit?usp=sharing>.
The document is open for commenting by anyone, and if you want editor
access - please send me your google account in a PM on Slack (@Dev-iL).
d applying the fixes suggested in the
exception messages themselves. I got around fixing 2-3 of them
before posting on the devlist. I will, however, go over it before
making further attempts.
Best,
Dev-iL
On 2025/06/26 19:48:25 Jens Scheffler wrote:
> Hi,
>
> thanks for taki
One tiny comment regarding TP's suggestion - IMHO it's better to avoid
`unittest.mock` in favor of the equivalent `mocker` fixture provided by
`pytest-mock`.
On 2025/07/10 06:30:22 Tzu-ping Chung wrote:
> Personally I dislike things like assert_called_once_with etc. since
they are easy to miss
e/airflow/pull/52518.
Thanks,
Dev-iL
On 2025/06/26 12:49:25 Dev iL wrote:
> Hello everyone,
>
> With the release of Airflow 3 and the refactoring that moved
> flask-appbuilder (FAB) into a separate provider, as well as recent
work by
> the FAB developers to support SQLAlchemy v2.0 (
might be possible to get this done in
time for 3.1.
I'd love your inputs on how to best approach this task. More importantly,
if anyone wants to participate - please leave your comment on my PR, and
let's coordinate. I suggest you use my branch as a starting point, since it
has the tests in p
Is there an existing example in the project of supporting multiple
library versions that require distinct approaches?
Best,
Dev-iL
On 2025/06/27 02:08:17 Wei Lee wrote:
> > 2. Should we work on supporting SQLA 2.0 or jump straight to 2.1 (which
> is currently in beta)?
>
> Unle
The below is a more organized writeup of a suggestion I once shared on
Slack. I figured it should be documented and discussed here as well. I am
currently developing something equivalent using a short-circuit operator,
but it would be nice for this to be a built-in functionality. An
illustration of
