-
Notifications
You must be signed in to change notification settings - Fork 493
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
Delete unported moveit_joy
visualization demo
#1541
Conversation
Codecov ReportBase: 50.24% // Head: 51.08% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1541 +/- ##
==========================================
+ Coverage 50.24% 51.08% +0.85%
==========================================
Files 374 380 +6
Lines 31277 31802 +525
==========================================
+ Hits 15712 16243 +531
+ Misses 15565 15559 -6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Good idea to address the setup.py deprecation warnings! I fear that removing these files might lead to dead code, for example the \python in moveit_core. @peterdavidfagan what do you think about this? Will the deprecation warning be addressed by your work on MoveIt2 python bindings?
Small misconception here:
All of this code is already dead! You're right, the Python code in |
moveit_joy
visualization demo
78195bc
to
fd9b003
Compare
Hi @sjahr, Thanks for looping me into this conversation.
I have actually removed this code in my current working branch of moveit_py (see here) so it would be ok to remove in my mind as @AndyZe has suggested. I can look to open a separate pr just for removing such code.
I am happy to address this as part of my GSoC project. For any of the code related to the library I am planning to release I would expect to ensure any warning including those related to deprecations to be addressed where they possibly can be. If existing code that is being maintained contains such deprecation warning I would be happy to fix these too. |
Thanks @peterdavidfagan. My bit of googling into this type of error suggested that it's a ROS2 build system issue and we need to wait for Open-Robotics to fix it. Nothing to be done on our end.
|
0e0a190
to
148587f
Compare
Description
I was poking around, looking into build warnings about deprecated
setup.py
. While I didn't find a complete solution, I think we can safely delete all of these scripts since they still refer tocatkin
.