Lines Matching +full:bazel +full:- +full:repo

1 # Python Rules for Bazel
3 …9ba7a1205955a45b53e854.svg?branch=main)](https://buildkite.com/bazel/python-rules-python-postsubmi…
7 This repository is the home of the core Python rules -- `py_library`,
9 support in Bazel. It also contains package installation rules for integrating with PyPI and other i…
14 [Bazel Build Encyclopedia](https://docs.bazel.build/versions/master/be/python.html).
18 Currently, the core rules build into the Bazel binary, and the symbols in this
19 …Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. Se…
21 The core rules are stable. Their implementation in Bazel is subject to Bazel's
22 [backward compatibility policy](https://docs.bazel.build/versions/master/backward-compatibility.htm…
26 …Bazel community maintains this repository. Neither Google nor the Bazel team provides support for …
30 - Status: Beta
31 - Full Feature Parity: No
38 the older way of configuring bazel with a `WORKSPACE` file.
45 your MODULE.bazel file:
74 is used by the version-unaware rules (e.g. `//python:py_binary.bzl` et al). For
75 submodules, it's recommended to use the version-aware rules to pin your programs
83 silently ignored if a submodule does it. Similarly, using the version-unaware
106 2. To allow incremental, per-target, upgrading to newer Python versions,
107    typically in a mono-repo situation.
109 To configure a submodule with the version-aware rules, request the particular
110 version you need, then use the `@python_versions` repo to use the rules that
126 …s under the [examples](examples) folder.  Look for the examples that contain a `MODULE.bazel` file.
130 The `python.toolchain()` call makes its contents available under a repo named
132 `python.toolchain(python_version="3.11")` creates the repo `@python_3_11`.
145 load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
158     strip_prefix = "rules_python-{}".format(VERSION),
159 …url = "https://github.com/bazelbuild/rules_python/releases/download/{}/rules_python-{}.tar.gz".for…
169 To register a hermetic Python toolchain rather than rely on a system-installed interpreter for runt…
192 …n targets will use the toolchain's interpreter during execution, but a system-installed interpreter
194 … this toolchain. Please refer to [python-build-standalone documentation's _Quirks_ section](https:…
198 …bazel rules, such as `genrule()`, by adding the `toolchains=["@rules_python//python:current_py_too…
218 1. [Installing third_party packages](#installing-third_party-packages)
219 2. [Using third_party packages as dependencies](#using-third_party-packages-as-dependencies
225 …bazel` file, use the `pip.parse` extension, and call it to create the central external repo and in…
240 … load the `pip_parse` function and call it to create the central external repo and individual whee…
245 # Create a central repo that knows about the dependencies needed from
259 …p_parse` is a repository rule and therefore executes pip at WORKSPACE-evaluation time, Bazel has no
270 re-executed to pick up a non-hermetic change to your environment (e.g.,
271 updating your system `python` interpreter), you can force it to re-execute by running
272 `bazel sync --only [pip_parse name]`.
276 …nts.txt` with a fully resolved set of dependencies using a tool such as `pip-tools` or the `compil…
280 Each extracted wheel repo contains a `py_library` target representing
283 repo's `//:requirements.bzl` file. This function maps a pip package
306 [this issue][requirements-drawbacks] for an enumeration. If you don't
316 Bazel label names (e.g. `-`, `.`) replaced with `_`. If you need to
330 [requirements-drawbacks]: https://github.com/bazelbuild/rules_python/issues/414
351 [Gazelle](https://github.com/bazelbuild/bazel-gazelle)
352 is a build file generator for Bazel projects. It can create new `BUILD.bazel` files for a project t…
354 Bazel may run Gazelle using the Gazelle rule, or it may be installed and run as a command line tool.
360 The core rules are currently available in Bazel as built-in symbols, but this
370 # Also consider using the -r flag to modify an entire workspace.
371 buildifier --lint=fix --warnings=native-py <files>
375 started](#Getting-started) above.
377 Note that Starlark-defined bundled symbols underneath