In places where we would have called asyncio.get_event_loop(), instead call osrf_pycommon.process_utils.get_loop(). Since the latter is already suppressing the warning, the warning will be quieted there.
Add some additional warning filters (in the tests) to catch the "There is no current event loop" warning. These will go away when we update to Python >= 3.11
Remove the create_future_impl utility. That was only needed for compatibility with Python < 3.6, which we have no instances of anymore. This particular change also requires a change to launch_ros.
With these changes in place, there are no more warnings coming from the launch tests.
Depends on https://github.com/ros2/launch_ros/pull/372
To do that, we do 3 things:
asyncio.get_event_loop()
, instead callosrf_pycommon.process_utils.get_loop()
. Since the latter is already suppressing the warning, the warning will be quieted there.create_future_impl
utility. That was only needed for compatibility with Python < 3.6, which we have no instances of anymore. This particular change also requires a change tolaunch_ros
.With these changes in place, there are no more warnings coming from the
launch
tests.