Bugfix: Broken dependency resolution due to removed python 3.8 support in rules_python
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system
Research direction
Reproduce the failure with bazel run //:docs, then inspect the score_bazel_tools_python 0.1.3 MODULE.bazel reference at the linked registry URL and the rules_python 1.8.0 changelog. Trace the python_3_8 import and determine the compatible behavior for newer rules_python versions; done means dependency resolution no longer requests the unavailable repository.
Written by the indexing model from the issue text.
Description
When using score_bazel_tools_python 0.1.3 (which references rules_python 1.4.1) in a repository that specifices a version of rules_python >= 1.8.0, this breaks. Due to dependency resolution following "Minimal Version Selection", the newer rules_python version is taken.
That is also the case if a recent score_docs_as_code (>=3.0.0) is referenced, as this itself references rules_python 1.8.3:
https://github.com/eclipse-score/docs-as-code/blob/main/MODULE.bazel#L22
The support of python 3.8 was dropped in rules_python 1.8.0, leading to the failure
https://rules-python.readthedocs.io/en/latest/changelog.html#v1-8-0
I guess that's valid since python 3.8 support from the python core team was stopped in October 2024.
In score_bazel_tools_python there is the implicit assumption that python 3.8 support from rules_python exists.
Either that should be removed or reworked.
Actual error message:
~/score/inc_someip_gateway$ bazel run //:docs
ERROR: module extension @@rules_python+//python/extensions:python.bzl%python does not generate repository "python_3_8", yet it is imported as "bazel_tools_python_python_3_8" in the usage at https://raw.githubusercontent.com/eclipse-score/bazel_registry/main/modules/score_bazel_tools_python/0.1.3/MODULE.bazel:74:23 (did you mean 'python_3_9'?)
INFO: Elapsed time: 0.814s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target
[!IMPORTANT]
Make sure to link this issue with the PR for your bugfix.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-score/bazel-tools-python
-
eclipse-score/bazel-tools-python#20 · 1 assignee ·
All issues in eclipse-score/bazel-tools-python
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·