Limit Python prek hooks to use Python 3.10

[potiuk]

We have inline project metadata in the prek hooks, and that means that each of the scripts will use their own venv to roon. However Airflow code and libraries does not support Python 3.14 yet (and will not for quite a while - because our dependencies will need time to catch-up. In the meantime we have to limit prek hooks to not install Python 3.14.

Actually in order to have good stability, we are fine to limiting
EVERYONE to use Python 3.10 for prek. There are no real benefits from
using a different Python version (except maybe a little speed but
prek-hooks are generally rather fast anyway) and we can definitely
benefit from better stability and having exactly the same output
for prek hooks by everyone. Uv will handle installation of the
right python version automatically.

Fixes: #56048

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Can we go for py 3.13 instead for all these?

[potiuk]

Can we go for py 3.13 instead for all these?

No. Because our Python code base supports 3.10 so we have to go for lowest common denominator.

[potiuk]

Can we go for py 3.13 instead for all these?

No. Because our Python code base supports 3.10 so we have to go for lowest common denominator.

For example the whole reason why things started to fail for the user in #56048 (look closely) - is that the code we were using in regular Airflow was using some things that were removed in 3.14.

Now - if we allow people to run their check on 3.13 - and we have some code that does not work on 3.10 - it will work for them but it will not be python 3.10 compliant.

So absolutely safest choice is to have everyone use the same as the lowest denominator for Airflow code - Python 3.10.

Even if Python 3.13 works a bit faster and has better UX for developers (it does) - the "works for me" problem is far bigger than any of the gains.

In this case - optimisation goal is not for this to be "better" - but to be "the same for everyone" (and compatible with the code we write for Airflow).

[potiuk]

And it has almost (besides a little speed) almost 0 impact for anyone to be perfectly honest, so I am not sure what we would gain from 3.13 support here:

• those scripts are mostly throwaway and nowadays mostly AI generated - so I don't care about using too many new language features
• you will not notice it when you run it - Python 3.10 will be automatically downloaded and installed by uv under the hood
• you can still - if you want - run those scripts manually using higher version of Python if you care for better debugging/UX experieonce - nothing (including IDE support) prevents you from doing so - inline script metadata is largely optional, it will still work fine if you have Python 3.13 venv and run the script there.

So frankly, I do not see practically any benefit of having 3.13 there.. But maybe I missed something?

[ashb]

Nope, nothing more than "py 3.13 runs 5-50% faster" but I agree with the reasons you listed, it's not worth it. (I was just thinking "most of the scripts are not really tied to what version of python we support, they just do things like read files or check AST etc" but most != all.

[jscheffl]

Thanks for the constructive and not heated discussion. I fully agree to arguments and outcome! LGTM.

[github-actions]

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

[potiuk]

Thanks for the constructive and not heated discussion. I fully agree to arguments and outcome! LGTM.

Heated ? Have you seen heated discussion between us 😄 ?

[johnslavik]

Noticed another one similar to #58439 (comment)

Suggested change

	# # requires-python = ">=3.10,<3.11"
	# requires-python = ">=3.10,<3.11"

@potiuk I think this wasn't intentional?

[johnslavik]

PR #59047