cleanup

Author: aignas

python/uv/private/lock.bzl

@@ -380,11 +380,15 @@ def lock(
       action.
     - `name.run`: a runnable target that can be used to pass extra parameters
       to the same command that would be run in the `name` action. This will
-      update the source copy of the requirements file.
+      update the source copy of the requirements file. You can customize the
+      args via the command line, but it requires being able to run `uv` (and
+      possibly `python`) directly on your host.
     - `name.update`: a target that can be run to update the source-tree version
       of the requirements lock file. The output can be fed to the
       {obj}`pip.parse` bzlmod extension tag class. Note, you can use
-      `native_test` to wrap this target to make a test.
+      `native_test` to wrap this target to make a test. You can't customize the
+      args via command line, but you can use RBE to generate requirements
+      (offload execution and run for different platforms)
 
     Args:
         name: {type}`str` The prefix of all targets created by this macro.
@@ -440,7 +444,6 @@ def lock(
         update_target = update_target,
         output = out,
         tags = [
-            "local",
             "manual",
             "no-cache",
             "requires-network",
@@ -463,16 +466,18 @@ def lock(
     # FIXME @aignas 2025-03-20: is it possible to extend `py_binary` so that the
     # srcs are generated before `py_binary` is run? I found that
     # `ctx.files.srcs` usage in the base implementation is making it difficult.
+    template_target = "_{}_gen".format(name)
     _expand_template(
-        name = name + "_cp",
+        name = template_target,
         src = name,
         output = out,
         update_target = update_target,
+        tags = ["manual"],
     )
 
     py_binary(
         name = update_target,
-        srcs = [name + "_cp"],
+        srcs = [template_target],
         data = [name] + ([maybe_out] if maybe_out else []),
         tags = ["manual"],
     )