Lines Matching +full:runtime +full:- +full:versions

1 ---
4 created: 2019-02-12
5 updated: 2019-02-21
7   - [brandjon@](https://github.com/brandjon)
9 …- [katre@](https://github.com/katre), [mrovner@](https://github.com/mrovner), [nlopezgi@](https://…
11 ---
17 ….build/versions/master/toolchains.html). This replaces the previous mechanism of explicitly specif…
19 …-related definitions are implemented in Starlark. A byproduct of this is that the provider type fo…
23 …he native Python rules use the toolchain framework to resolve the Python runtime. Advantages inclu…
25 * allowing each `py_binary` to use a runtime suitable for its target platform
27 … same build without [hacks](https://github.com/bazelbuild/bazel/issues/4815#issuecomment-460777113)
29 * making it easier to run Python-related builds under remote execution
33 * removing `--python_top` and `--python_path`
37 **Non-goal:** This work does not allow individual `py_binary`s to directly name a Python runtime to…
43 A new [toolchain type](https://docs.bazel.build/versions/master/toolchains.html#writing-rules-that-…
45 …ype are expected to return a [`ToolchainInfo`](https://docs.bazel.build/versions/master/skylark/li…
57 …-exposed Starlark name of the native provider returned by the [`py_runtime`](https://docs.bazel.bu…
59 …runtime* or an *in-build runtime*. A platform runtime accesses a system-installed interpreter at a…
61 …versions/master/be/platform.html#constraint_setting)s to act as a standardized namespace for this …
65 * `interpreter_path`: If this is a platform runtime, this field is the absolute filesystem path to …
67 * `interpreter`: If this is an in-build runtime, this field is a `File` representing the interprete…
69 …-build runtime, this field is a depset of `File`s that need to be added to the runfiles of an exec…
77 … be loaded from `@bazel_tools//tools/python:toolchain.bzl`. It has two label-valued attributes, `p…
81 …versions/master/be/python.html#py_binary) and [`py_test`](https://docs.bazel.build/versions/master…
83 Since `--python_top` is no longer read, it is deprecated. Since `--python_path` was only read when …
85 Implementation wise, the native `PyRuntimeProvider` is turned into the user-visible `PyRuntimeInfo`…
89 …-by cleanup (and non-breaking change), the `files` attribute of `py_runtime` is made optional. For…
93 …versions/master/be/platform.html#toolchain) of last resort, `@bazel_tools//tools/python:autodetect…
97 …le that defines a platform whose Python interpreters are located under a non-standard path. The ex…
127 # Python runtime definitions that reify these system paths as BUILD targets.
149     # Since the Python interpreter is invoked at runtime on the target
185 bazel build //pkg:my_pybin --platforms=//platform_defs:my_platform
194 …--incompatible_use_python_toolchains`, is created to assist migration. When the flag is enabled, `…
198 …attribute for `py_binary`, i.e. `PY3` if `--incompatible_py3_is_default` is true and `PY2` otherwi…
202 #### How can I force a `py_binary` to use a given runtime, say for a particular minor version of Py…
204 …yPy), compilation modes (optimized, debug), an interpreter linked with a pre-selected set of exten…
212 …ributes in the user-facing toolchain rule, i.e. `py_runtime_pair`, because it's a very common use …
214 …runtime is chosen is to introduce additional constraints on the toolchain, and let toolchain resol…
216 … a massive `select()`. But the first approach is much more feasible to implement in the short-term.
224 …ted by the Python rules, and then by defining new user-facing toolchain rules that serve as front-…
238 …'s workspace by Bazel. This follows precedent for other languages with built-in support in Bazel. …
243 ------------ | ------
244 2019-02-12   | Initial version
245 2019-02-14   | Make `PyRuntimeInfo` natively defined
246 2019-02-15   | Clarify platform runtime vs in-build runtime
247 2019-02-21   | Formal approval