In Python 3 __ne__ by default delegates to __eq__ and inverts the
result, but in Python 2 they urge you to define __ne__ when you
define __eq__ for it to work properly [1].There are no implied
relationships among the comparison operators. The truth of x==y
does not imply that x!=y is false. Accordingly, when defining
__eq__(), one should also define __ne__() so that the operators
will behave as expected.
[1]https://docs.python.org/2/reference/datamodel.html#object.__ne__
Reviewed: https:/ /review. openstack. org/337445 /git.openstack. org/cgit/ openstack/ python- smaugclient/ commit/ ?id=7b16de49083 71cad5c15445511 32eac34758315f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7b16de4908371ca d5c1544551132ea c34758315f
Author: yuyafei <email address hidden>
Date: Tue Jul 5 15:37:56 2016 +0800
Add __ne__ built-in function
In Python 3 __ne__ by default delegates to __eq__ and inverts the /docs.python. org/2/reference /datamodel. html#object. __ne__
result, but in Python 2 they urge you to define __ne__ when you
define __eq__ for it to work properly [1].There are no implied
relationships among the comparison operators. The truth of x==y
does not imply that x!=y is false. Accordingly, when defining
__eq__(), one should also define __ne__() so that the operators
will behave as expected.
[1]https:/
Change-Id: Iae22095146e640 81f362601665284 b43d0056f48
Closes-Bug: #1586268