0.8.0

WORKSPACE setup:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_python",
    sha256 = "9fcf91dbcc31fde6d1edb15f117246d912c33c36f44cf681976bd886538deba6",
    strip_prefix = "rules_python-0.8.0",
    url = "https://github.com/bazelbuild/rules_python/archive/refs/tags/0.8.0.tar.gz",
)

BREAKING CHANGES

In 0.7.0 we introduced the hermetic Python interpreter toolchain, with a repository rule python_register_toolchains that generated a "magically-named" repo with _resolved_interpreter as the suffix, like this:

python_register_toolchains(
    name = "python3_9",
    # Available versions are listed in @rules_python//python:versions.bzl.
    # We recommend using the same version your team is already standardized on.
    python_version = "3.9",
)
load("@python3_9_resolved_interpreter//:defs.bzl", "interpreter")

In 0.8.0 that suffix is removed, so the resolved toolchain is just named the same as you provide. In that example the last line would now be

load("@python3_9//:defs.bzl", "interpreter")

What's Changed

• release: Fix release snippet by @alexeagle in #651
• docs: avoid users on 3.10 by accident by @alexeagle in #653
• fix: take custom tools versions into account when selecting Python interpreter by @mattem in #654
• Allow for custom python versions in python_register_toolchains by @UebelAndre in #657
• Update CODEOWNERS. remove andy scott as maintainer by @thundergolfer in #658
• Document how to vendor a pip_parse requirements.bzl file by @alexeagle in #655
• Expose defs.bzl form resolved_interpreter_os_alias as a target by @UebelAndre in #659
• Allow python_register_toolchains.name to be the resolved interpreter repo by @UebelAndre in #656
• Fix annotations_test on windows systems that don't support symlinks by @UebelAndre in #665
• Added support for custom strip_prefix args in toolchains by @UebelAndre in #664
• Updated pip, pkginfo, setuptools, and wheel. by @UebelAndre in #661

Full Changelog: 0.7.0...0.8.0