bazel-contrib / bazel-contrib/rules_python
Define wheel version via file/target
- Lenguaje dominante
- Starlark
- Estrellas
- 688
- Forks
- 721
- Merge medio
- 15 h 7 min
- PR fusionados (30 d)
- 76
Descripción
# 🚀 feature request
### Relevant Rules
* py_wheel
### Description
I would like use wheel version generated by other target.
### Describe the solution you'd like
```
my_version_generator(
name = "version"
...
)
py_wheel(
name = "foo",
version_file = ":version",
...
)
```
Solution should be a bit similiar to https://github.com/vaticle/bazel-distribution/blob/ebb4a9b342ec442c427705ec6a7919cce4c35c6e/maven/rules.bzl#L258
### Describe alternatives you've considered
* Generating version before build and passing via variable in volatile status. Solution is inconvenient for multiple modules and is against bazel design.
Guía de contribución
Línea de trabajo
Start by locating the py_wheel rule and reviewing how its current version is configured. Compare the requested version_file target behavior with the linked maven/rules.bzl example; done means a generated target can provide the wheel version, including support for multiple modules.
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
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100