bazel-contrib / bazel-contrib/rules_python

Allow using a locally installed Python runtime as a full toolchain

Abierto
#2,070 7 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Starlark
Estrellas
688
Forks
721
Merge medio
15 h 7 min
PR fusionados (30 d)
76

Descripción

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

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza revisando el PR #2000 y los elementos TODO completados para asignar una instalación local de Python a Bazel. Define la API pública y los parámetros necesarios a partir de los casos de uso documentados y, después, determina cómo admitir la creación de un entorno in-build en lugar del runtime de la plataforma.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
build-system
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.