-
Notifications
You must be signed in to change notification settings - Fork 44
DeviceAttribute.is_empty was not working correctly with latest cpp tango version #273
Conversation
…ion (fixes issue-271)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the PR should be against develop
, not stable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick fix @jairomoldes (and remembering a cppTango change from a year an a half ago!)
You are right. Sorry. My mistake. |
@tiagocoutinho This has been fixed, so I'm going to merge this. |
- Verify basic reading and writing of spectrum attributes. - Verify that clients reading empty spectrum attributes get a `None` value. The string spectrum attriubte is a special case as it doesn't reduce its length when written to. Relates to issue tango-controls#271, and PR tango-controls#273
Just one comment: |
@cpascual Thanks for the comment - that sounds like an issue you need to raise in https://github.com/tango-controls/cppTango |
By principle, PyTango tries not to change the behaviour of the C++ library. Since a backward compatibility was introduced, I also think that the previous behaviour should be restored at the C++ level. Regardless of the C++ team decision, this PR should be reverted because it masks some behaviour changes. |
Agree that PyTango behaviour should match the C++ library, but don't agree that this PR makes PyTango behave differently. It makes PyTango's behaviour more accurate. If the C++ library indicates that an attribute is empty, PyTango now correctly matches that behaviour. Importantly, it makes PyTango's behaviour consistent with its previous behaviour.
I don't think this PR should be reverted. That would break PyTango functionality. With this patch, PyTango works correctly with the C++ library 9.2.x and 9.3.x. Why would we want to lose that? |
fixes #271