• Home
Name Date Size #Lines LOC

..--

other_module/06-Sep-2024-4821

runfiles/06-Sep-2024-8756

.bazelignoreD06-Sep-202413 21

.bazelrcD06-Sep-2024237 106

.bazelversionD06-Sep-20246 21

.gitignoreD06-Sep-20248 21

BUILD.bazelD06-Sep-20243.6 KiB9990

MODULE.bazelD06-Sep-20243.6 KiB8876

README.mdD06-Sep-20241.1 KiB2921

WORKSPACED06-Sep-2024101 32

__main__.pyD06-Sep-2024691 193

__test__.pyD06-Sep-2024874 3414

gazelle_python.yamlD06-Sep-202420.6 KiB592586

lib.pyD06-Sep-2024680 203

requirements.inD06-Sep-2024101 76

requirements_lock.txtD06-Sep-202414.9 KiB228227

requirements_windows.txtD06-Sep-202415.1 KiB232231

README.md

1# Bzlmod build file generation example
2
3This example demostrates how to use `rules_python` and gazelle with `bzlmod` enabled.
4[Bzlmod](https://bazel.build/external/overview#bzlmod), the new external dependency
5subsystem, does not directly work with repo definitions. Instead, it builds a dependency
6graph from modules, runs extensions on top of the graph, and defines repos accordingly.
7
8Gazelle is setup with the `rules_python`
9extension, so that targets like `py_library` and `py_binary` can be
10automatically created just by running:
11
12```sh
13$ bazel run //:gazelle update
14```
15
16The are other targets that allow you to update the gazelle dependency management
17when you update the requirements.in file.  See:
18
19```bash
20bazel run //:gazelle_python_manifest.update
21```
22
23For more information on the behavior of the `rules_python` gazelle extension,
24see the [README.md](../../gazelle/README.md) file in the /gazelle folder.
25
26This example uses a `MODULE.bazel` file that configures the bzlmod dependency
27management. See comments in the `MODULE.bazel` and `BUILD.bazel` files for more
28information.
29