Sonins commented on pull request #20508: URL: https://github.com/apache/airflow/pull/20508#issuecomment-1043303110
> @Sonins how curial is this fix for you ? and why? thinking about it... even in your current Airflow version (whatever that may be) you should not use `days_ago`. We will deprecate it soon but regardless - what prevents you from simply not using it? Thus avoiding the problem all together. `days_ago` has its simplicity even considering the implied problem you guys pointed out. Because of that, ([as Bas pointed out](https://lists.apache.org/thread/5l15l5qz5jzsbq589zjrxnlycgyjs120)) a lot of people may still uses it regardless its problem, but It has been problem that days_ago only run in timezone UTC. I thought some people felt uncomfortable about it, so I suggested this fix. I don't understand 'curial' mean but that was why I open this pr. I realized `days_ago` has a problem after I opened this pr so i'm not using it anymore. But still fix is fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
