If it’s not defined in rclpy then it’s probably not defined anywhere. I don’t know off the top of my head where this was being used in rospy, but it may make sense to have it in rclpy and it simply hasn’t been ported yet. It might be connected to the init/shutdown or rate features that are still missing.
It is missing, but those issues I don’t think are the best connection to that feature. I’d say:
Which is being worked on now:
Yes, that issue specifically mentions Timer and Rate concepts, which are dependent on finishing the “ROS Time” implementation in rclpy.
It’s not been explicitly removed as far as I know, it just hasn’t been implemented yet. You could use try_shutdown() to test, but if you only wanted to test you’d be out of luck since the side-effect would be a shutdown in many cases. This feature is captured in this issue (in my opinion):
Which it seems you’ve already found and offered to help (thanks!).