potiuk commented on code in PR #46891:
URL: https://github.com/apache/airflow/pull/46891#discussion_r2203529655
##########
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:
Yes - it's really a gray zone between what "users" need and what
"maintainers" need - the version in pyproject.toml is essentially serving both
cases:
* for users good idea is to block things if they are not supported on
certain python version
* but for maintainers it means that we need to do actions to open-up if we
upper-bind it - even if we do not have to
I think now the best strategy will be:
"airflow-core" + "airflow" + "task-sdk" -> we should likely add
`<3.NEXT_VERSION" - we **know** it will take time to make airflow-core
compatible - if only, because we know that a number of providers and 3rd-party
dependencies will make Airflow unusable on the NEXT_VERSION. Typicallly it
takes 4-7 monhts to be able to say "we support it even if some remaining
providers don't".
* providers - we do not put upper bind by definition. Those providers won't
be installable on NEXT_VERSION until `task-sdk`this will (currently also
airflow-core) will suppport NEXT_VERSION
* but we can explicitly exclude a version pf provider if we know provider is
not compatible. With != 3.X - it shoutld not be <= = but !- to make it explicit
that we are waiting for comatibility issues to be foxed. We already had cases
where we excluded nto LATEST but OLDEST version for some cases - and != seems
to be good for that.
--
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]
