bazel-contrib / bazel-contrib/rules_python

Evaluate the best extraction method for repository rules

Aperta
#3,562 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Starlark
Stelle
688
Fork
721
Merge medio
15h 7m
PR unite (30g)
76

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
python, rust
Ambito
build-system, tooling
Tipo di issue
Refactoring
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.