bazel-contrib / bazel-contrib/rules_python
Integrate sys.abi_features/sys.abi_info into toolchains when available
- Langage dominant
- Starlark
- Étoiles
- 688
- Forks
- 721
- Merge moyen
- 15 h 7 min
- PR mergées (30 j)
- 76
Description
It looks like Python is going to add a `sys.abi_info` attribute that gives details about the interpreter's ABI.
https://discuss.python.org/t/add-sys-abi-features-to-make-information-about-the-interpreter-abi-more-accessible/94422
https://github.com/python/cpython/pull/137476
Whatever they do, It should be exposed on our toolchains. We already do something similar for `sys.abiflags`; this new fields is basically a more structured and improved version of it.
* [ ] Add a equivalent field on the toolchain type, since it's specific about the C ABI, it should go on the py-cc toolchain type.
* [ ] local_toolchains: inspect it and put its values in the toolchain
* [ ] python-build-standalone: ideally, this would go into a file we can read a repo time using starlark. (cross builds may mean the interpreter can't be run directly)
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start with the existing sys.abiflags handling and the py-cc toolchain type, then inspect local_toolchains and python-build-standalone as named in the checklist. Compare the proposed sys.abi_features/sys.abi_info behavior in the linked Python discussions and determine how values can be supplied for cross builds; done means the ABI information is exposed on toolchains when available.
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é
- Plutôt claire
- Accessibilité débutants
- 35/100