tree 3d914263ee14b253e3ded9b859c2c46994411fe4
parent fe2c3256ddb51ad04d6af70e1cec59770a29596e
author Ignas Anikevicius <anikevicius@gmail.com> 1687550725 +0900
committer GitHub <noreply@github.com> 1687550725 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJklfsVCRBK7hj4Ov3rIwAAqqAIAEqq0892v/JEUO1yLVzy/hXs
 V3f5GFe/iXlDDK9Amuyouk5DTUZmjozoJwyD2RcDkTNQDFSvoqXJfvySgh/Qfset
 qS46KL2r4JZotW5wnDD5rtVKeY9yeu0hm+VKS5ahHCUFEkMDey6FALJOXEbATnMh
 HfXGz2Pdz7WuEiUA149SBh0zesjqZeAMIcZTSZBOHs3bNBO7e6tB/47RufbYUKee
 cG9FhYRdCDTPjoThvFI0o7DFP43ZPIIVay8pcYZq1KBv1QYUJ9jLB3LOkMsPY+8X
 jx+vSWXTJK5LZggjH4zOMrJah8vBWoTjt4dK7l+O5wO4Z8PipP/2Y7bIKvQn5Bo=
 =NKm2
 -----END PGP SIGNATURE-----
 

fix(toolchain): restrict coverage tool visibility under bzlmod (#1252)

Before this PR the `coverage_tool` automatically registered by
`rules_python`
was visible outside the toolchain repository. This fixes it to be
consistent
with `non-bzlmod` setups and ensures that the default `coverage_tool` is
not
visible outside the toolchain repos.

This means that the `MODULE.bazel` file can be cleaned-up at the expense
of
relaxing the `coverage_tool` attribute for the `python_repository` to be
a
simple string as the label would be evaluated within the context of
`rules_python` which may not necessarily resolve correctly without the
`use_repo` statement in our `MODULE.bazel`.