-
Notifications
You must be signed in to change notification settings - Fork 589
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
python-can 3.3.4 breaks functionality in a minor version #919
Comments
Thanks for reporting, if there is a clean way to still support custom attributes l'm happy to make a quick 3.3.5 release. I'll note that we documented custom attributes on the Message class haven't been supported since the 3.0 release (See the Message docs)
@karlding this was introduced from fixing #804, ensuring a message can be pickled. Any ideas for how can we might continue to support both custom attributes and pickling? |
Thanks for the quick reply. For some reason I don't think I've ever seen one of the deprecation warnings, so I wasn't aware of this change. On my side I've updated my code to use a subclass of |
Is there still some action needed on this? |
I don't think any PRs were opened to fix 3.3.4, and there haven't been any other comments in half a year so I think it is safe to close. |
Commit 0c34e50 introduced this change in
message.py
This effectively disables the use of custom attributes in
Message
. It seems that's planned for version 4.0, but this change breaks any code that adds attributes toMessage
and does so in a patch version instead of a major one.The text was updated successfully, but these errors were encountered: