bazel-contrib / bazel-contrib/rules_python
Define wheel version via file/target
- Vorherrschende Sprache
- Starlark
- Sterne
- 688
- Forks
- 721
- Ø Merge
- 15 Std. 7 Min.
- Gemergte PRs (30 T.)
- 76
Beschreibung
# 🚀 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.
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- build-system
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100