airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jarek Potiuk <Jarek.Pot...@polidea.com>
Subject Re: Changed behaviour of Timezone DST in Python 3.6 vs. 3.5
Date Sun, 14 Apr 2019 07:42:55 GMT
After a bit of diffing it seems it's a different reason Local Time
disambiguation changed in Python 3.6:
https://docs.python.org/3/whatsnew/3.6.html#pep-495-local-time-disambiguation

https://pendulum.eustace.io/docs/#using-the-timezone-library-directly  -
seems that pendulum which we use backported 'fold' behaviour to 3.5 and it
does not mix and match well with working directly with timezone in python
3.5.

J.


On Sun, Apr 14, 2019 at 9:28 AM Jarek Potiuk <Jarek.Potiuk@polidea.com>
wrote:

> Hello Airflowers.
>
> While testing the multi-staging docker I've found an incompatibility
> problem between python 3.5 and 3.6 w/regards to Timezone DST. Seems related
> to a known TZ behaviour change in Python 3.6
> https://bugs.python.org/issue30062
>
> I created a JIRA issue for it:
> https://issues.apache.org/jira/browse/AIRFLOW-4308 but it's not entirely
> obvious whether the problem is in the test or it's a real Airflow problem.
>
> Before I dig deeper, maybe someone who is more familiar with the timezone
> tests/code can shed some light on this ? I use the Simplified Development
> Workflow environment to test it and I have repeatable behaviour so I can
> very quickly retest it if someone can suggest some solutions :)
>
> J.
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>


-- 

Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer

M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message