-
Notifications
You must be signed in to change notification settings - Fork 911
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
rospy uses depracated warn() instead of warning() (important; with patch) #2106
Comments
@mikolajz Thanks for the report and patch file! Would you be willing to open a pull request directly? |
Sorry for the delay, this got lost in the e-mails around Christmas, but now I've created the PR #2120 . |
Resolved by #2120 |
Thanks. What is the release schedule for ROS? Can we expect this patch to be released in DEB packages for ROS Noetic, or will it be part of some ROS Oxxx? I'm asking since we have a patch in our local Docker image and wonder when we should prepare for it not to apply cleanly. |
@mikolajz You can expect this patch in an update to Noetic. It's hard to give a timeline for the next release, but I can try and at least make a source release and get it into testing sometime next week. |
In Ubuntu 20.04 with ROS Noetic, running code using
rospy
results in a lot of warnings like:The attached patch fixes it.
The surprising part is that this is important for us, as when we run our
pytest
in Ubuntu 20.04, we get more such warnings than the default scrolling buffer of the terminal, thus we don't see the other messages above.rospy.diff.txt
The text was updated successfully, but these errors were encountered: