jscheffl commented on code in PR #46891:
URL: https://github.com/apache/airflow/pull/46891#discussion_r2203526736
##########
airflow-core/pyproject.toml:
##########
@@ -35,7 +35,7 @@ name = "apache-airflow-core"
description = "Core packages for Apache Airflow, schedule and API server"
readme = { file = "README.md", content-type = "text/markdown" }
license-files.globs = ["LICENSE", "3rd-party-licenses/*.txt", "NOTICE"]
-requires-python = ">=3.10,!=3.13"
+requires-python = ">=3.10"
Review Comment:
Makes sense.
Just with the side effect - assume Airflwo 3.1 is released w/o upper
binding, then with 3.2 we realize it is not working and we exclude it in a 3.2
release, then in Python 3.14 if you do pip install it will install Airflow
3.1... and fail. But okay, I think we can live with this.
It is the problem as a "gray zone" of what is between "officially supported"
and "known being in-compatible".
--
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]
