You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What does this mean exactly? score wants to officially support 2.x or we want to force all our users to have to use 2.x?
For the second I do not believe that score is ready for that. See for example eclipse-score/tooling#430
I would start with making sure that score supports users using rules_python 2.x and then we can consider for how long we want to keep support for 1.x and announce it accordingly.
maybe this is the same discussion as we had today in the TL sync regarding gtest ... so IMHO it is one discussion if score wants to update and use rules_python 2.x for the tooling (docs-as-code, etc.) but as a "user" in an ECU project I maybe have different tooling needs or have some own tooling (sphinx) setup with different needs ... but this then requires an according dev_dependencies setup to not enforce it.
This issue is exactly to track that and is part of the new alignment board (link on the right side). I've included some issues for user relevant updates. Don't really care about dev dependencies.
Activity
limdor commentedon Oct 12, 2026
What does this mean exactly? score wants to officially support 2.x or we want to force all our users to have to use 2.x?
For the second I do not believe that score is ready for that. See for example eclipse-score/tooling#430
I would start with making sure that score supports users using rules_python 2.x and then we can consider for how long we want to keep support for 1.x and announce it accordingly.
umaucher commentedon Oct 12, 2026
maybe this is the same discussion as we had today in the TL sync regarding gtest ... so IMHO it is one discussion if score wants to update and use rules_python 2.x for the tooling (docs-as-code, etc.) but as a "user" in an ECU project I maybe have different tooling needs or have some own tooling (sphinx) setup with different needs ... but this then requires an according dev_dependencies setup to not enforce it.
AlexanderLanin commentedon Oct 12, 2026
This issue is exactly to track that and is part of the new alignment board (link on the right side). I've included some issues for user relevant updates. Don't really care about dev dependencies.