Consistently exclude Python 3.14 #58657
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since UV and other installers essentially ignore < limit in the python-requires, a good practice is to simply exclude current Python versions that we **know** we are not compatible with rather than using <. Python 3.14 is a thing now and people will get it by default as latest versions, but we do not run our tests with Python 3.14 yet (not until March/April 2026). Providers have all upper-bind exclusion except those that do not support Python 3.13, but that's ok because they are actually limited by Airflow they can be installed on. But for distributions like airflow-ctl, we should explicitly exclude 3.14 until we support and test it. This PR synchronizes all python-requires in non-provider distribution to consistently exclude Python 3.14 with !=.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
dstandish,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jason810496,
jedcunningham,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:airflow-ctl
area:API
Closed
bugraoz93
approved these changes
Nov 25, 2025
Contributor
|
Thanks Jarek! Let's merge this first. I can rebase and check document part in the other |
Member
Author
Yep. |
Member
Author
|
Also for posterity - astral-sh/uv#14711 is where we had a long and somewhat heated discussion with Astral team on why upper-binding is ignored by |
Copilot AI
pushed a commit
to jason810496/airflow
that referenced
this pull request
Dec 5, 2025
Since UV and other installers essentially ignore < limit in the python-requires, a good practice is to simply exclude current Python versions that we **know** we are not compatible with rather than using <. Python 3.14 is a thing now and people will get it by default as latest versions, but we do not run our tests with Python 3.14 yet (not until March/April 2026). Providers have all upper-bind exclusion except those that do not support Python 3.13, but that's ok because they are actually limited by Airflow they can be installed on. But for distributions like airflow-ctl, we should explicitly exclude 3.14 until we support and test it. This PR synchronizes all python-requires in non-provider distribution to consistently exclude Python 3.14 with !=.
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
Since UV and other installers essentially ignore < limit in the python-requires, a good practice is to simply exclude current Python versions that we **know** we are not compatible with rather than using <. Python 3.14 is a thing now and people will get it by default as latest versions, but we do not run our tests with Python 3.14 yet (not until March/April 2026). Providers have all upper-bind exclusion except those that do not support Python 3.13, but that's ok because they are actually limited by Airflow they can be installed on. But for distributions like airflow-ctl, we should explicitly exclude 3.14 until we support and test it. This PR synchronizes all python-requires in non-provider distribution to consistently exclude Python 3.14 with !=.
24 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since UV and other installers essentially ignore < limit in the python-requires, a good practice is to simply exclude current Python versions that we know we are not compatible with rather than using <.
Python 3.14 is a thing now and people will get it by default as latest versions, but we do not run our tests with Python 3.14 yet (not until March/April 2026). Providers have all upper-bind exclusion except those that do not support Python 3.13, but that's ok because they are actually limited by Airflow they can be installed on. But for distributions like airflow-ctl, we should explicitly exclude 3.14 until we support and test it.
This PR synchronizes all python-requires in non-provider distribution to consistently exclude Python 3.14 with !=.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.