bazel-contrib / bazel-contrib/rules_python
Consolidate where dev-only tools and things live
- 主要言語
- Starlark
- スター
- 688
- フォーク
- 721
- 平均マージ
- 15時間 7分
- マージ済み PR(30日)
- 76
説明
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?
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- tooling
- issue の種類
- リファクタリング
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100