| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| foo/ | 04-Jul-2025 | - | 1 | 0 | ||
| BUILD.in | D | 04-Jul-2025 | 76 | 3 | 2 | |
| BUILD.out | D | 04-Jul-2025 | 372 | 16 | 12 | |
| README.md | D | 04-Jul-2025 | 458 | 7 | 5 | |
| WORKSPACE | D | 04-Jul-2025 | 55 | 2 | 1 | |
| __init__.py | D | 04-Jul-2025 | 0 | 1 | 0 | |
| test.yaml | D | 04-Jul-2025 | 608 | 16 | 1 |
README.md
1# Project generation mode with tests 2 3Example using `gazelle:python_generation_mode project` in a project with tests, but no `__test__.py` entrypoint. 4 5Note that, in this mode, the `py_test` rule will have no `main` set, which will fail to run with the standard 6`py_test` rule. However, this can be used in conjunction with `gazelle:map_kind` to use some other implementation 7of `py_test` that is able to handle this sitation (such as `rules_python_pytest`).