aris") +
>> timedelta(hours=8)
>> DateTime(2023, 3, 26, 7, 0, 0, tzinfo=Timezone('Europe/Paris'))
>>
>> I don't want to get in a discussion about design, I just want to point
>> out from a user perspective of using Airflow this will be shocking,
>
want to get in a discussion about design, I just want to point out
> from a user perspective of using Airflow this will be shocking, especially
> if macros might return a pendulum.datetime or a datetime.datetime under
> different contexts.
>
> -Original Message-
> From: Tz
I just want to point out from
a user perspective of using Airflow this will be shocking, especially if macros
might return a pendulum.datetime or a datetime.datetime under different
contexts.
-Original Message-----
From: Tzu-ping Chung
Sent: Thursday, February 20, 2025 12:09 PM
To: dev@airf
> That said, I agree the maintenance situation with Pendulum is dire and
> untenable, but I just want to make it clear that for users which take
> advantage of Airflow's time zone support it may be a non-trivial and error
> prone process to convert to the standard library.
>
&g
age-
From: Jarek Potiuk
Sent: Thursday, February 20, 2025 8:17 AM
To: dev@airflow.apache.org
Subject: Re: [DISCUSS] Python 3.13 support
One more finding which I miss..
* Pendulum - the elephant in the room (I like that phrase, yes).
I saw that Ash had already been involved in discussions abo
One more finding which I miss..
* Pendulum - the elephant in the room (I like that phrase, yes).
I saw that Ash had already been involved in discussions about Python 3.13
support for pendulum in the PR that my friend from DLTHub started -
https://github.com/python-pendulum/pendulum/pull/871 - but
This is the time of the year when we attempt to see how far we are from
supporting minor python version released in October (i.e. Python 3.13 now).
Usually it takes a couple of months before we can even try - because of the
number of dependencies - and it was no different this time around.
For now
