potiuk opened a new pull request #19334: URL: https://github.com/apache/airflow/pull/19334
In order to keep consistency, both mypy and flake were always using Python 3.6 - simply to make sure that the same errors are produced for everyone. When default python version was changed in #19317 the regular PR static checks started to fail because Python 3.6 image is no longer built for "regular" PRs (it's only built when "full-tests-needed" is set or when the build runs in "main" as result of push or schedule). Unfortunately those "defaults" could not be read from "default python version" easily, because they are also executed in pre-commits, which do not have the same initialization as `breeze` or other CI scripts so there are literally 3 more places where Python 3.6 should be changed to 3.7. This PR fixes it. <!-- Thank you for contributing! 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 committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
