| commit | 24052387ec57f15e510b14dd5c4bee07f6db6dc0 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Mon Oct 31 14:16:35 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 31 14:17:45 2022 -0700 |
| tree | 83222a6daf7352404a6122047ca1daebb2f0360d | |
| parent | a8d0d5061fe5c2b783532e472fc4741683aa97e8 [diff] |
Add py_builtins and py_internal helper namespaces in Bazel to allow Starlark to use Java helpers * `py_builtins` is an Starlark builtins-internal-only namespace for functions that only builtins should use. * `py_internal` is for regular Starlark for testing and other esoteric purposes. Usage of this is restricted to packages relating to the rule implementations to prevent using these internal APIs. (These already exist in the Google-internal build; this makes them defined in Bazel, too, though they're currently no-ops; followup CLs will begin moving common code out of the Google-py_internal and into the common one). Work towards #15897 PiperOrigin-RevId: 485146419 Change-Id: I71902e60471a4227c1993778bda60cbbe6e316f0
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
