Skip to content

upkeep: update rules_python to 2.2.0 - #430

Closed
a-zw wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:update-rules-python
Closed

upkeep: update rules_python to 2.2.0#430
a-zw wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:update-rules-python

Conversation

@a-zw

@a-zw a-zw commented Aug 18, 2026

Copy link
Copy Markdown

Needed for compatibility with score_docs_as_code.

@LittleHuba LittleHuba left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many users are still on rules_python 1.x.x
Updating here to 2.x.x ist a significant breaking change that is not aligned in the S-Core project on project level.

@a-zw

a-zw commented Aug 19, 2026

Copy link
Copy Markdown
Author

Ok, closing this again.

I thought docs-as-code already required rules_python 2+ but I just saw it working with the old one.

@a-zw a-zw closed this Aug 19, 2026
@a-zw
a-zw deleted the update-rules-python branch August 19, 2026 06:54
@limdor

limdor commented Aug 19, 2026

Copy link
Copy Markdown

FYI, this is the issue we were getting last time I tried in score communication when using rules_python 2.0.3
eclipse-score/communication#695
I did not dig deeper but it seemed that the problem was comming from score tooling. @a-zw are you sure that score tooling is ready to work with rules_python 2.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants