Name Date Size #Lines LOC

..--

other_module/H25-Apr-2025-4821

runfiles/H25-Apr-2025-8958

.bazelignoreH A D25-Apr-202513 21

.bazelrcH A D25-Apr-2025203 95

.gitignoreH A D25-Apr-20258 21

BUILD.bazelH A D25-Apr-20253.4 KiB9283

MODULE.bazelH A D25-Apr-20253.6 KiB8876

README.mdH A D25-Apr-20251.1 KiB2921

WORKSPACEH A D25-Apr-2025101 32

__main__.pyH A D25-Apr-2025691 193

__test__.pyH A D25-Apr-2025873 3414

gazelle_python.yamlH A D25-Apr-2025756 3630

lib.pyH A D25-Apr-2025680 203

requirements.inH A D25-Apr-2025101 76

requirements_lock.txtH A D25-Apr-202515 KiB230228

requirements_windows.txtH A D25-Apr-202515.2 KiB234232

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