jml-derek
diff --git a/‎README.md
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions b/‎README.md
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
diff --git a/‎docs/python.md
Copy file name to clipboardExpand all lines: docs/python.md
+23Lines changed: 23 additions & 0 deletions b/‎docs/python.md
Copy file name to clipboardExpand all lines: docs/python.md
+23Lines changed: 23 additions & 0 deletions
diff --git a/‎python/BUILD
Copy file name to clipboardExpand all lines: python/BUILD
+6Lines changed: 6 additions & 0 deletions b/‎python/BUILD
Copy file name to clipboardExpand all lines: python/BUILD
+6Lines changed: 6 additions & 0 deletions
diff --git a/‎python/defs.bzl
Copy file name to clipboardExpand all lines: python/defs.bzl
+43Lines changed: 43 additions & 0 deletions b/‎python/defs.bzl
Copy file name to clipboardExpand all lines: python/defs.bzl
+43Lines changed: 43 additions & 0 deletions
diff --git a/‎tests/load_from_macro/BUILD
Copy file name to clipboardExpand all lines: tests/load_from_macro/BUILD
+8Lines changed: 8 additions & 0 deletions b/‎tests/load_from_macro/BUILD
Copy file name to clipboardExpand all lines: tests/load_from_macro/BUILD
+8Lines changed: 8 additions & 0 deletions
@@ -83,6 +83,11 @@ After registration, your Python targets will use the toolchain's interpreter dur
 is still used to 'bootstrap' Python targets (see https://github.com/bazelbuild/rules_python/issues/691).
 You may also find some quirks while using this toolchain. Please refer to [python-build-standalone documentation's _Quirks_ section](https://python-build-standalone.readthedocs.io/en/latest/quirks.html) for details.
 
+### Toolchain usage in other rules
+
+Python toolchains can be utilised in other bazel rules, such as `genrule()`, by adding the `toolchains=["@rules_python//python:current_py_toolchain"]` attribute. The path to the python interpreter can be obtained by using the `$(PYTHON2)` and `$(PYTHON3)` ["Make" Variables](https://bazel.build/reference/be/make-variables). See the [`test_current_py_toolchain`](tests/load_from_macro/BUILD) target for an example.
+
+
 ### "Hello World"
 
 Once you've imported the rule set into your `WORKSPACE` using any of these
 
@@ -24,6 +24,8 @@ In an ideal renaming, we'd move the packaging rules to a different package so
 that @rules_python//python is only concerned with the core rules.
 """
 
+load(":defs.bzl", "current_py_toolchain")
+
 package(default_visibility = ["//visibility:public"])
 
 licenses(["notice"])  # Apache 2.0
@@ -138,3 +140,7 @@ exports_files([
     "packaging.bzl",
     "pip.bzl",
 ])
+
+current_py_toolchain(
+    name = "current_py_toolchain",
+)
@@ -41,6 +41,49 @@ def _add_tags(attrs):
         attrs["tags"] = [_MIGRATION_TAG]
     return attrs
 
+def _current_py_toolchain_impl(ctx):
+    toolchain = ctx.toolchains[ctx.attr._toolchain]
+
+    direct = []
+    transitive = []
+    vars = {}
+
+    if toolchain.py3_runtime and toolchain.py3_runtime.interpreter:
+        direct.append(toolchain.py3_runtime.interpreter)
+        transitive.append(toolchain.py3_runtime.files)
+        vars["PYTHON3"] = toolchain.py3_runtime.interpreter.path
+
+    if toolchain.py2_runtime and toolchain.py2_runtime.interpreter:
+        direct.append(toolchain.py2_runtime.interpreter)
+        transitive.append(toolchain.py2_runtime.files)
+        vars["PYTHON2"] = toolchain.py2_runtime.interpreter.path
+
+    files = depset(direct, transitive = transitive)
+    return [
+        toolchain,
+        platform_common.TemplateVariableInfo(vars),
+        DefaultInfo(
+            runfiles = ctx.runfiles(transitive_files = files),
+            files = files,
+        ),
+    ]
+
+current_py_toolchain = rule(
+    doc = """
+    This rule exists so that the current python toolchain can be used in the `toolchains` attribute of
+    other rules, such as genrule. It allows exposing a python toolchain after toolchain resolution has
+    happened, to a rule which expects a concrete implementation of a toolchain, rather than a
+    toolchain_type which could be resolved to that toolchain.
+    """,
+    implementation = _current_py_toolchain_impl,
+    attrs = {
+        "_toolchain": attr.string(default = str(Label("@bazel_tools//tools/python:toolchain_type"))),
+    },
+    toolchains = [
+        str(Label("@bazel_tools//tools/python:toolchain_type")),
+    ],
+)
+
 def py_library(**attrs):
     """See the Bazel core [py_library](https://docs.bazel.build/versions/master/be/python.html#py_library) documentation.
 
 
@@ -24,3 +24,11 @@ py_library(
     # Allow a test to verify an "outside package" doesn't get included
     visibility = ["//examples/wheel:__pkg__"],
 )
+
+genrule(
+    name = "test_current_py_toolchain",
+    srcs = [],
+    outs = ["out.txt"],
+    cmd = "$(PYTHON3) --version > $(location out.txt)",
+    toolchains = ["//python:current_py_toolchain"],
+)