bazel-contrib / bazel-contrib/rules_python

Evaluate the best extraction method for repository rules

Offen
#3,562 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Starlark
Sterne
688
Forks
721
Ø Merge
15 Std. 7 Min.
Gemergte PRs (30 T.)
76

Beschreibung

Alternatives:
* What we have in legacy - Python interpreter + `installer` whl
* What we have in pipstar - `repository_ctx.extract` + `chmod` and `repository_ctx.rename`
* What `uv` is using - https://github.com/astral-sh/uv/blob/0.9.28/crates/uv-extract/src/sync.rs
* A regular `uutils` chmod + unzip

For the last thing we would probably have to setup:
- development rust toolchain.
- binary archiving as part of release. We could probably download the right thing and store hashes using the new `facts` API for `bzlmod`.
- download the binary as a dependency to `whl_library`.

This is a followup to #3554 and #3555.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by reading follow-ups #3554 and #3555, then compare the legacy Python interpreter and installer wheel path, pipstar's repository_ctx.extract/chmod/rename path, uv's crates/uv-extract/src/sync.rs, and the uutils chmod/unzip option. Check the release, whl_library, and bzlmod facts API implications described in the issue. Done means selecting and documenting a justified extraction approach with its toolchain, dependency, binary-release, and hash requirements.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python, rust
Bereich
build-system, tooling
Issue-Typ
Refactoring
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.