Update known stdlibs with python 3.15

[ShaharNaveh]

Follow up on #21119 (comment)

[ShaharNaveh]

I got an error when running from the scripts directory.
I can revert this if it's an issue.

[MichaReiser]

Thank you.

I'm not sure if it makes sense to update the stdlib if Ruff doesn't have support for Python 3.15. I think I'd prefer to wait for when we add Python 3.15 support once the beta is closer, to ensure that we don't ship with a stale stdlib for 3.15

[ShaharNaveh]

Thank you.

I'm not sure if it makes sense to update the stdlib if Ruff doesn't have support for Python 3.15. I think I'd prefer to wait for when we add Python 3.15 support once the beta is closer, to ensure that we don't ship with a stale stdlib for 3.15

Sure, feel free to close this PR if you think it's just noise in the PR pool ATM.

---

What is the approach when supporting a new Python version? When will users can set python-version = "PY315" for example? (even if it's still considered experimental)

Does ruff have a contributer's guide on when to implement support for new Python versions?

[MichaReiser]

What is the approach when supporting a new Python version? When will users can set python-version = "PY315" for example? (even if it's still considered experimental)

In the past, we waited for the new Python version to be closer to beta to avoid implementing features that don't end up being stabilized (or have to change the semantics multiple times).

Does ruff have a contributer's guide on when to implement support for new Python versions?

We don't have a contributor guide for adding support for a new Python version but you can search for the python314 label to see the relevant PRs for adding Python 3.14. That should give you a good idea on how we go about it.