build: support python 3.13

[anakin87]

Related Issues

• fixes Remove restriction python<3.13 in pyproject.toml #8825

I experimented with Python 3.13 locally (Ubuntu) and in a draft PR (#8959; Ubuntu, MacOs, Windows).

What I found

• our core dependencies work well with Python 3.13 except for Spacy (and, to some extent, Whisper).
• Spacy (used in the NamedEntityExtractor) is not yet compatible: Spacy installation on python 3.13 fails explosion/spaCy#13658.
• Whisper has some installation issues with uv (but works with pip): uv fails to compile proper --universal txt file with openai-whisper astral-sh/uv#6852
• Contributors using Python 3.13 will encounter errors when installing test dependencies due to Spacy and Whisper.
• In my opinion, this shouldn't prevent final users from using Python 3.13.

Proposed Changes:

• support Python 3.13 and communicate it

How did you test it?

CI; if you are curious, check also tests in #8959.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 13672865207

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 90.218%

---

Totals
Change from base Build 13652854933:	0.002%
Covered Lines:	9601
Relevant Lines:	10642

---

💛 - Coveralls

[sjrl]

Would it be best practice to add ,<3.14? Or should we only restrict it once new versions of python come out and we figure out then that the version doesn't work?

[anakin87]

In hindsight, perhaps it was a mistake to restrict to Python <3.13 (done by me in #8547). I would prefer not to officially support python 3.14 but leave users free to experiment and report errors when this version becomes available.

[sjrl]

sounds good to me!

[sjrl]

Could we add a bit more explanation for why less than 3.13? Or rather say all tests (or the testing dev env) will not run locally if using python 3.13. They could theoretically contribute to Haystack still and just rely on our CI to run tests.

[anakin87]

95cdee4

[sjrl]

Thanks! This looks good to me