tree 6c98e2ff4ede333a79305cf634815406cbc7272e
parent 8aaaf9303cb962fa1ec613051cccdfa56a077847
author Richard Levasseur <rlevasseur@google.com> 1704629602 -0800
committer GitHub <noreply@github.com> 1704629602 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlmpVyCRBK7hj4Ov3rIwAAF3gIAEzfrYUGnPDZTi6dQtPJsS6f
 6AJrCNi+h4TZwnRlFbigC8pM3ITyesglBsqsclgS88/s/xXi9eH38y6UqaD1HRMm
 BTP4W6YWOUkYyNrSon7NFSYOfwlR9JU1PtkCbxlYCpEojhzPYvO5i5tgmKCaLTSJ
 TjBTcEBrKGOlP2iP2DiN3r2bB/WyTteQAISb39KpnhWf1QSpkxNBpsdWXZ1X/0uk
 LaEg75tQXnsmhX9yvp8+lTBXPiwsb/dd7dG8iZ9R5wMnKXxj6inxUvSQCu3Swcog
 mvcUOU1VIQ09iqCcWSJvijuW/KXRnrvr6kEp+czE0d0phW5RQB4O5zqs1eRiBZk=
 =IlzE
 -----END PGP SIGNATURE-----
 

fix(toolchains): register py cc toolchain for workspace builds (#1670)

The workspace `python_register_toolchains()` function only registered
the plain Python toolchain by its specific name. The py cc toolchain
wasn't also being named. This meant things like
`//python/cc:current_py_cc_headers` couldn't find their toolchain.
Bzlmod doesn't have this problem because it uses the `:all` pattern to
register everything.

To fix, also register the py cc toolchain where the plain Python
toolchain is registered, which makes it available.

Fixes https://github.com/bazelbuild/rules_python/issues/1669