| commit | 68c30483f80a55870eb113e17ab21ff65d5b97ed | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Tue Jul 16 16:22:22 2024 -0700 |
| committer | GitHub <noreply@github.com> | Tue Jul 16 23:22:22 2024 +0000 |
| tree | 0c6f11a3e3b67f63778053aee796bba772d2fa01 | |
| parent | 68f752e3fb141f520978ad86f3f0e155c3502a20 [diff] |
internal: repos to create a toolchain from a locally installed Python (#2000) This adds the primitives for defining a toolchain based on a locally installed Python. Doing this consists of two parts: * A repo rule to define a Python runtime pointing to a local Python installation. * A repo rule to define toolchains for those runtimes. The runtime repos create platform runtimes, i.e, it sets py_runtime.interpreter_path. This means the runtime isn't included in the runfiles. Note that these repo rules are largely implementation details, and are definitely not stable API-wise. Creating public APIs to use them through WORKSPACE or bzlmod will be done in a separate change (there's a few design and behavior questions to discuss). This is definitely experimental quality. In particular, the code that tries to figure out the C headers/libraries is very finicky. I couldn't find solid docs about how to do this, and there's a lot of undocumented settings, so what's there is what I was able to piece together from my laptop's behavior. Misc other changes: * Also fixes a bug if a pyenv-backed interpreter path is used for precompiling: pyenv uses `$0` to determine what to re-exec. The `:current_interpreter_executable` target used its own name, which pyenv didn't understand. * The repo logger now also accepts a string. This should help prevent accidentally passing a string causing an error. It's also just a bit more convenient when doing development. * Repo loggers will automatically include their rule name and repo name. This makes following logging output easier. * Makes `repo_utils.execute()` report progress. * Adds `repo_utils.getenv`, `repo_utils.watch`, and `repo_utils.watch_tree`: backwards compatibility functions for their `rctx` equivalents. * Adds `repo_utils.which_unchecked`: calls `which`, but allows for failure. * Adds `repo_utils.get_platforms_os_name()`: Returns the name used in `@platforms` for the OS reported by `rctx`. * Makes several repo util functions call `watch()` or `getenv()`, if available. This makes repository rules better respect environmental changes. * Adds more detail to the definition of an in-build vs platform runtime * Adds a README for the integration tests directory. Setting up and using one is a bit more involved than other tests, so some docs help. * Allows integration tests to specify bazel versions to use.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.