bazel-contrib / bazel-contrib/rules_python

Allow using a locally installed Python runtime as a full toolchain

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

Descrizione

This feature request has come up a few time from different places.

The basic request is to have an option other than the hermetic runtimes, typically a Python runtime that is locally installed. Some of the reasons this is appealing:

* Avoids having to download a remote runtime.
* If you deeply care about supply chain issues, the provenance of the runtimes isn't very compelling.
* The standalone-python-build runtimes have some known limitations
* The hermetic runtimes are expensive to setup: they're inbuild runtimes with a (mostly) full python installation, all of which has to be copied into runfiles
* I think some people like to manage their Python version outside of bazel, e.g. using `pyenv` or venv activation.

Making a local runtime have the same capabilities as a hermetic runtime is _sort of_ possible today, but requires quite a bit of setup, and I think maybe loading a few private bzl files.

PR #2000 lays the ground work for most of it. What's now missing is a public API for it and figuring out what knobs (if any) it needs.

For at least early testing, we're thinking to have a flag control what type of runtime is selected.

But, during our maintainers meeting, two big questions came up:
1. What does the public API for using it look like?
2. What are the use cases? These drive what the public API needs to look like

So, if you have use cases, please post them here. It'll help us figure out what capabilities are needed.

TODO
* [x] Create repo rules to map the local python install into bazel
* [x] Allow setting arbitrary target_compatible_with/target_settings
* [ ] Allow creating an in-build instead of platform runtime

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start by reviewing PR #2000 and the completed TODO items for mapping a local Python installation into Bazel. Define the public API and required knobs from the documented use cases, then determine how to support creating an in-build rather than platform runtime.

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

Valutazione

Stack tecnologico
python
Ambito
build-system
Tipo di issue
Funzionalità
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.