chore: update location of toolchain type, accounting for rules_python breaking change

Author: alexeagle

examples/BUILD.bazel

@@ -1,6 +1,6 @@
 load("@rules_go//proto:def.bzl", "go_proto_library")
 load("@rules_proto//proto:defs.bzl", "proto_library")
-load("@rules_python//python:proto.bzl", "py_proto_library")
+load("@protobuf//bazel:py_proto_library.bzl", "py_proto_library")
 
 package(default_visibility = ["//visibility:public"])
 

examples/MODULE.bazel

@@ -2,12 +2,20 @@ bazel_dep(name = "toolchains_protoc", version = "0.0.0")
 bazel_dep(name = "aspect_bazel_lib", version = "2.11.0")
 bazel_dep(name = "aspect_rules_py", version = "1.3.2")
 bazel_dep(name = "platforms", version = "0.0.11")
+bazel_dep(name = "protobuf", version = "29.3")
 bazel_dep(name = "rules_java", version = "8.6.3")
 bazel_dep(name = "rules_proto", version = "7.1.0")
 bazel_dep(name = "rules_python", version = "1.2.0-rc0")
 bazel_dep(name = "rules_go", version = "0.53.0")
 bazel_dep(name = "rules_uv", version = "0.56.0")
 
+# Need https://github.com/bazelbuild/rules_python/pull/2620
+git_override(
+    module_name = "rules_python",
+    commit = "e95f95f75c9078f252f5b03eca18cba12d2e2166",
+    remote = "[email protected]:alexeagle/rules_python.git",
+)
+
 # This example is in the same repo with the ruleset, so we should point to the code at HEAD
 # rather than use any release on the Bazel Central Registry.
 local_path_override(