feat(toolchain): add python 3.13.0, updated other versions and bumped coverage to 7.6.1

[vfdev-5]

Description:

• Added python 3.13.0 toolchain
• Updated other versions in the toolchain
• Bumped coverage version to 7.6.1
• Updated CHANGELOG.md

[aignas]

If you run the target defined in https://github.com/bazelbuild/rules_python/blob/413690fd09b068ab43ec9c1d37d20d8017747f2c/python/private/BUILD.bazel#L509 then rules_python will download all of the toolchains and print the checksums. The only thing you need to have is the list of empty platform identifiers, like:

    "3.13.0": {
        "url": "20240909/cpython-{python_version}rc2+20240909-{platform}-{build}.tar.gz",
        "sha256": {
            "aarch64-apple-darwin": "",
            "aarch64-unknown-linux-gnu": "",
            "ppc64le-unknown-linux-gnu": "",
            "s390x-unknown-linux-gnu": "",
            "x86_64-apple-darwin": "",
            "x86_64-pc-windows-msvc": "",
            "x86_64-unknown-linux-gnu": "",
        },
        "strip_prefix": "python",
    },

Sorry for being late here.

I think you also need to change any reference to MINOR_MAPPING, which is using the values in the folowing way. I think it is the only place. Adding a new Python version is always slightly annoying.

[aignas]

And I see that a new release was cut that includes rc3: https://github.com/indygreg/python-build-standalone/releases/tag/20241002

[vfdev-5]

@aignas thanks for the review! I agree there was something weird in the last commit in addition to a merge conflict with CHANGELOG.md. I fixed it and now it should be good.

[aignas]

It seems that they were really fast: https://github.com/indygreg/python-build-standalone/releases/tag/20241008 contains the new builds and even the free-threading ones. I think adding the freethreading values in the TOOL_VERSIONS should be done in #2129.

[aignas]

Could you also please add new binaries for coverage.py? This is needed since it is a new major version of python. I think just upgrading to the latest version (https://pypi.org/project/coverage/#files) should be sufficient. The docs on how to do it are in DEVELOPING.md file.

Feel free to leave notes there about how to add a new minor python version.

[vfdev-5]

Could you also please add new binaries for coverage.py? This is needed since it is a new major version of python. I think just upgrading to the latest version (https://pypi.org/project/coverage/#files) should be sufficient. The docs on how to do it are in DEVELOPING.md file.

Feel free to leave notes there about how to add a new minor python version.

I'm not very sure how this works, I updated the PR, please review

[aignas]

LGTM, thanks!