a68d6df930
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__ Change-Id: I3df4396495e3404e2c644c769693f89b7c01537a |
||
---|---|---|
.. | ||
tests | ||
__init__.py | ||
apply_config.py | ||
collect_config.py | ||
config_exception.py | ||
oac_file.py | ||
renderers.py | ||
value_types.py | ||
version.py |