bazel-contrib / bazel-contrib/rules_python
Consolidate where dev-only tools and things live
- Lenguaje dominante
- Starlark
- Estrellas
- 688
- Forks
- 721
- Merge medio
- 15 h 7 min
- PR fusionados (30 d)
- 76
Descripción
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?
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- tooling
- Tipo de issue
- Refactorización
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100