-
Notifications
You must be signed in to change notification settings - Fork 13
Replace Maven dependency with python native proto binding and submodule workflow #62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Maven dependency with python native proto binding and submodule workflow #62
Conversation
…dency, Upgraded code for latest up-spec 7af90bd9aee517e79b7a41427d37de28af0f6de0
- Removed Maven dependency references in README as they are no longer needed. - Updated instructions to reflect using `up-spec` as a git submodule. - Added steps to run `scripts/generate_proto.py` for generating local Python proto bindings. - Aligned workflow with the new approach of managing `up-core-api` protos locally instead of pulling during build. - Ensured instructions remain clean for new contributors while reflecting the deprecated proto subscribe handling updates.
AnotherDaniel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Some minor mostly editorial comments...
generate_proto.py
Outdated
| @@ -0,0 +1,67 @@ | |||
| """ | |||
| SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update to 2025
|
Code coverage report is ready! 📈
|
AnotherDaniel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you!
Summary
This PR modernizes the up-python build and development workflow by:
Motivation
Notes
Let me know if further adjustments are needed or if you prefer additional documentation updates. Thank you for reviewing!