• Home
Name Date Size #Lines LOC

..--

random_number_generator/04-Jul-2025-8228

.bazelrcD04-Jul-2025379 117

.gitignoreD04-Jul-20258 21

BUILD.bazelD04-Jul-20253.8 KiB10294

README.mdD04-Jul-2025800 2317

WORKSPACED04-Jul-20255.5 KiB135112

__init__.pyD04-Jul-2025961 3010

__main__.pyD04-Jul-2025670 193

__test__.pyD04-Jul-2025981 3211

gazelle_python.yamlD04-Jul-20251 KiB3832

requirements.inD04-Jul-202543 43

requirements_lock.txtD04-Jul-202516.4 KiB255254

requirements_windows.txtD04-Jul-202516.6 KiB261260

README.md

1# Build file generation with Gazelle
2
3This example shows a project that has Gazelle setup with the rules_python
4extension, so that targets like `py_library` and `py_binary` can be
5automatically created just by running
6
7```sh
8bazel run //:requirements.update
9bazel run //:gazelle_python_manifest.update
10bazel run //:gazelle
11```
12
13As a demo, try creating a `__main__.py` file in this directory, then
14re-run that gazelle command. You'll see that a `py_binary` target
15is created in the `BUILD` file.
16
17Or, try importing the `requests` library in `__init__.py`.
18You'll see that `deps = ["@pip//pypi__requests"]` is automatically
19added to the `py_library` target in the `BUILD` file.
20
21For more information on the behavior of the rules_python gazelle extension,
22see the README.md file in the /gazelle folder.
23