-
Notifications
You must be signed in to change notification settings - Fork 126
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
Support empy3 and empy4 #821
Conversation
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
I took this for a spin locally. I have good news and bad news. The good news is that this works, and seems to keep compatibility with both Empy 3 and Empy 4. The bad news is that with Empy 4, there is at least one bug. In particular, every time a rosidl_generator_py template file is expanded, it is printed to the console. This makes the output when building with it extremely noisy. I haven't dug into what is causing this, but I think we should find a way to fix/suppress this before we merge this in. |
Signed-off-by: Chris Lalancette <[email protected]>
I noticed this, That's why is still a draft |
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
@clalancette should be fixed now |
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
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.
One more thought, then I think we are good to run CI on this.
if em_has_configuration: | ||
interpreter.string(content, locals=kwargs) | ||
else: | ||
interpreter.string(content, str(template_path), kwargs) |
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.
Sorry, I just noticed one more thing. This looks different from both line 243, and line 193 above. I'm wondering if we should just make this consistent with everything else:
interpreter.string(content, str(template_path), kwargs) | |
interpreter.string(content, template_path, locals=kwargs) |
What do you think?
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.
Signed-off-by: Alejandro Hernández Cordero <[email protected]>
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.
This looks good to me, but I'm going to suggest we do a full CI run here (i.e. no --packages-above-and-dependencies
). That's just because this is so deep in the rosidl pipeline, I want to make sure everything works.
should we backport this to Jazzy, Iron, and Humble? Or they should use |
AFAIK, ubuntu nobel and jammy both use or do you have any specific requirement for this backporting? |
No I don't. We can wait. |
@Mergifyio backport jazzy |
✅ Backports have been created
|
Signed-off-by: Alejandro Hernández Cordero <[email protected]> (cherry picked from commit e25750d)
Signed-off-by: Alejandro Hernández Cordero <[email protected]> (cherry picked from commit e25750d) Co-authored-by: Alejandro Hernández Cordero <[email protected]>
No description provided.