amoghrajesh opened a new pull request, #60808: URL: https://github.com/apache/airflow/pull/60808
<!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [x] No --- While not a very common practice, users had to import from the internal execution_time path: `from airflow.sdk.execution_time.macros import ds_add` to use macros for utils / custom operator code which required manipulating date/time utilities which macros offered. I am making a change to expose this better with a short hand: `from airflow.sdk import macros`, this will allow users to use a simpler public API. One example use case I came across: ```python from airflow.sdk import macros, DAG from datetime import datetime start_date = macros.ds_add("2024-01-01", -7) with DAG("my_dag", start_date=start_date): ``` Simple example of usage: ```python from airflow.sdk.execution_time import macros macros.ds_add("2026-01-01", 7) Out[3]: '2026-01-08' from airflow.sdk import macros macros.ds_add("2026-01-01", 7) Out[5]: '2026-01-08' ``` * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). -- 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]
