bazel-contrib / bazel-contrib/rules_python
Allow using a locally installed Python runtime as a full toolchain
- Langage dominant
- Starlark
- Étoiles
- 688
- Forks
- 721
- Merge moyen
- 15 h 7 min
- PR mergées (30 j)
- 76
Description
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
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par examiner la PR #2000 et les éléments TODO terminés pour mapper une installation Python locale dans Bazel. Définissez l'API publique et les paramètres requis à partir des cas d'utilisation documentés, puis déterminez comment prendre en charge la création d'un environnement in-build plutôt que du runtime de la plateforme.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- build-system
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100