- 
                Notifications
    You must be signed in to change notification settings 
- Fork 141
          Provide base classes in rosidl_pycommon
          #887
        
          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
  
    Provide base classes in rosidl_pycommon
  
  #887
              Conversation
Signed-off-by: Michael Carlstrom <[email protected]>
Signed-off-by: Michael Carlstrom <[email protected]>
Signed-off-by: Michael Carlstrom <[email protected]>
Signed-off-by: Michael Carlstrom <[email protected]>
Signed-off-by: Michael Carlstrom <[email protected]>
| Pulls: ros2/rosidl_python#230, #887 | 
Signed-off-by: Michael Carlstrom <[email protected]>
| Pulls: ros2/rosidl_python#230, #887 | 
| @christophebedard The CI looks promising. I think aarch CI crashed. | 
| I found the job that was automatically triggered after the failure. Looks good, merging! | 
Description
See ros2/rosidl_python#230
The original issue ros2/rosidl_python#215 recommended placing the base classes in
rosidl_pycommonand that seemed reasonable to me.Is this user-facing behavior change?
Did you use Generative AI?
Additional Information