• Home
Name Date Size #Lines LOC

..--

random_number_generator/06-Sep-2024-8130

.bazelrcD06-Sep-2024154 64

.gitignoreD06-Sep-20248 21

BUILD.bazelD06-Sep-20244.1 KiB10799

README.mdD06-Sep-2024800 2317

WORKSPACED06-Sep-20245.2 KiB124102

__init__.pyD06-Sep-2024933 279

__main__.pyD06-Sep-2024670 193

__test__.pyD06-Sep-2024994 2911

gazelle_python.yamlD06-Sep-20243.4 KiB119113

requirements.inD06-Sep-20246 21

requirements_lock.txtD06-Sep-20244.9 KiB7978

requirements_windows.txtD06-Sep-20245.2 KiB8382

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