Python 3.15 support

[flying-sheep]

Description

Hi, 3.15 is upcoming, and I have two thoughts:

1. should we start supporting pre-releases like uv does? Currently you can just do uv venv -p 3.15 and it’ll install beta 2
2. for seamlessness, even if we don’t do alphas and betas, maybe doing rcs makes sense?

Use case/motivation

When 3.14 released, we didn’t have it for a while, which broke peoples’ CI. Would be nice to have 3.15 support on day 1.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow the Python Software Foundation's Code of Conduct

[cjames23]

I am in favor of making new interpreter versions available once they hit rcs

[flying-sheep]

I think pre-releases shouldn’t be included in the default hatch test matrix, but if people enable them manually by overriding the matrix, they should work.

Us supporting rcs will then allow people to opt-in to testing with (an rc of) an upcoming version on or before day 1 of the release, in a way that’ll automatically switch them to the final version when Hatch adds support for that.

Having betas would allow that even earlier, but that would increase maintenance cost further. Maybe in the future we could host the Python distribution data somewhere so Hatch can support new versions without updating it itself.

[cjames23]

I like the idea of eventually being able to have hatch support new versions without having to update itself each time. I do also want to start testing 3.15 on hatch's codebase itself.

[flying-sheep]

Once ofek/pyapp#233 is merged, we’re ready for this.

[cjames23]

This has shipped in 1.18.0 for rc1