Add support for Python 3.14

[cdce8p]

Breaking change

The following integrations won't work with Python 3.14 initially. Support will be added back once the dependencies are updated.

• AppleTV
• Jabber (XMPP)
• Logitech Harmony Hub

The profiler.memory service is not available when using Python 3.14. It will return if and when guppy3 becomes Python 3.14 compatible.

Proposed change

Add initial support for Python 3.14.
The following integrations don't work yet.

• AppleTV depends on pyatv
  Requires an update to the pydantic config.
  Drop support for pydantic v1 postlund/pyatv#2736
• Jabber (XMPP) and Logitech Harmony Hub depend on slixmpp
  Needs to update pyo3 to 0.25.
  https://codeberg.org/poezio/slixmpp
  Update slixmpp to 1.12.0 #154872
• Profiler depends (partially) on guppy3==3.1.5
  Error building wheel for Python 3.14
  https://github.com/zhuyifei1999/guppy3
  3.1.5: build fails with Python 3.14 zhuyifei1999/guppy3#50

Notes for developers

Pydantic will only fully support Python 3.14 with v2 models. Old v1 models might still work, especially if no advanced features are used. It's nevertheless recommended to update all dependencies to use the newer v2 models.

Thanks

I've started working on the Python 3.14 support back in May, 5 months ago. Thanks to everyone who has contributed to it and helped make it possible to have a PR ready on the day of release, especially with over 1500 dependencies.

--
For reference the Python 3.13 update:

• Add support for Python 3.13 #129442

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[edenhaus]

Thanks @cdce8p 👍

[cdce8p]

@edenhaus Merged dev to trigger a new CI run. Just one failing test now which I believe is also flaky for 3.13.

tests/components/playstation_network/test_init.py::test_trophy_title_coordinator_play_new_game - KeyError: 'entity_picture'

[frenck]

It seems it be consistent though...

[cdce8p]

It seems it be consistent though...

Yes, but unrelated to Python 3.14. This is the last run on dev
https://github.com/home-assistant/core/actions/runs/18504217935/job/52729802804

[cdce8p]

All tests pass now

[frenck]

Thanks, @cdce8p 👍

../Frenck