a070f5b16c
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: Id2d32eedddbbbb91c6da6e36f12515972aa9e5a5
Python bindings to the CloudKitty API
- version
-
0.2
- Wiki
- IRC
-
#cloudkitty @ freenode
python-cloudkittyclient
This is a client library for CloudKitty built on the CloudKitty API.
It provides a Python API (the cloudkittyclient module).
Status
This project is highly work in progress.