bazel-contrib / bazel-contrib/rules_python
Consolidate where dev-only tools and things live
- Dominant language
- Starlark
- Stars
- 688
- Forks
- 721
- Avg merge
- 15h 7m
- Merged PRs (30d)
- 76
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
Research direction
Start by inventorying private/, dev/, and tools/private/, including the pyproject.toml, requirements, uv lock, and multirun target mentioned in the issue. Confirm the proposed layout with maintainers; done means dev-only tools and utilities are consolidated under dev and the ambiguous private locations are no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100