Test Python 3.14 in CI

[srittau]

[srittau]

Ideally I'd want to use something like continue-on-error: ${{ matrix.python-version == '3.14-dev' }}, but I don't think it's possible. (We could of course emulate this by changing the shell command, but I don't like that.)

[brianschubert]

but I don't think it's possible.

I think it might be? I saw something similar in the SQLAlchemy tests: https://github.com/sqlalchemy/sqlalchemy/blob/main/.github/workflows/run-test.yaml#L121

[srittau]

Huh, I tried that but VSCode flagged that as invalid and the GitHub docs didn't mention it. I'll change it.

[Daraan]

Can/should we add a warning in a failing case?

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#setting-a-warning-message

[srittau]

In principle I like the idea of a warning message, but I didn't want to complicate the CI scripts for now.

[brianschubert]

Can/should we add a warning in a failing case?

I think we get this for free - it seems an error annotation still gets emitted for the failing step even when the job doesn't fail: https://github.com/python/typing_extensions/actions/runs/14196009731

[python-cla-bot[bot]]

All commit authors signed the Contributor License Agreement.

[JelleZijlstra]

Working on a PR to make the 3.14 tests pass