bazel-contrib / bazel-contrib/rules_python
Consolidate where dev-only tools and things live
Open
- Dominant language
- Starlark
- Stars
- 688
- Forks
- 721
- Avg merge
- 14h 49m
- Merged PRs (30d)
- 81
Description
Currently, we have 3 places where dev-only tools and utilities live:
* private/ -- a multirun target to update requirements
* dev/ -- pyproject.toml, requirements, and uv lock
* tools/private/ -- various tools for dev-only purposes
I propose moving everything under dev. The rationale is that "private" is ambiguous -- do we mean "implementation detail" or "dev only" ?
@aignas thoughts?
Contributor guide
Assessment
This issue has not been assessed yet.