Skip to content

fix: add support for python 3.14#533

Merged
ssbarnea merged 1 commit intomainfrom
fix/py314
Oct 6, 2025
Merged

fix: add support for python 3.14#533
ssbarnea merged 1 commit intomainfrom
fix/py314

Conversation

@ssbarnea
Copy link
Copy Markdown
Member

@ssbarnea ssbarnea commented Oct 6, 2025

  • Ensures we fail fast with known unsupported versions of ansible-core
  • Prepares for fixing uv installation conflict due to unreleased conditional dependency

Related: astral-sh/uv#2685
Fixes: AAP-55147

@github-actions github-actions bot added fix and removed fix labels Oct 6, 2025
@ssbarnea ssbarnea disabled auto-merge October 6, 2025 12:20
@ssbarnea ssbarnea merged commit c1dfe75 into main Oct 6, 2025
20 of 22 checks passed
@ssbarnea ssbarnea deleted the fix/py314 branch October 6, 2025 12:21
core_version = Version(version("ansible-core"))
if core_version < Version("2.20.0dev0"): # pragma: no cover
msg = f"Python 3.14 requires ansible-core version >= 2.20.0, and we found {core_version}."
raise RuntimeError(msg)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. How is he setup known to be broken? I cannot find any information on this.
  2. It would be helpful if this check could be disabled by an environment variable.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did some tests with uncommenting the raise RuntimeError(...), so far it just worked fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants