delta/openstack/python-ceilometerclient.git/ceilometerclient/apiclient, branch 2.9.1 opendev.org: openstack/python-ceilometerclient.git Handle log message interpolation by the logger 2017-02-07T13:46:58+00:00 Gábor Antal antal@inf.u-szeged.hu 2017-02-07T13:45:49+00:00 2d0529347dd4060da127ce7d070819f2dc30055f According to OpenStack Guideline[1], logged string message should be interpolated by the logger. [1]: http://docs.openstack.org/developer/oslo.i18n/guidelines.html#adding-variables-to-log-messages Change-Id: Ia2bcd4387c406a3f7ffdb3cfe0badeccca22f278 Closes-Bug: #1661262 
According to OpenStack Guideline[1], logged string message should be
interpolated by the logger.

[1]: http://docs.openstack.org/developer/oslo.i18n/guidelines.html#adding-variables-to-log-messages

Change-Id: Ia2bcd4387c406a3f7ffdb3cfe0badeccca22f278
Closes-Bug: #1661262
Add __ne__ built-in function 2016-11-23T07:10:56+00:00 gecong1973 ge.cong@zte.com.cn 2016-11-23T07:10:56+00:00 d65d3312e6fb8dc752741c46cf5796f22497c593 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: I4ba5b370e34cd64b13d87ef3ce2869d224dd0969 
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: I4ba5b370e34cd64b13d87ef3ce2869d224dd0969
move old oslo-incubator code out of openstack/common 2016-11-05T00:18:45+00:00 Steve Martinelli s.martinelli@gmail.com 2016-10-29T16:05:26+00:00 c1141ed5be72ee169a7640b5d4957bfe02ad37ce As part of the first community-wide goal, teams were asked to remove the openstack/common package of their projects if one existed. This was a byproduct of the old oslo-incubator form of syncing common functionality. The package, apiclient, was moved to a top level location and a new i18n module was created. There is no oslo.apiclient library or equivalent, the recommended solution is to move it in tree and maintain it there. Change-Id: Ia788313e0926dc872a87b090ef0a350898bfb079 
As part of the first community-wide goal, teams were asked
to remove the openstack/common package of their projects
if one existed. This was a byproduct of the old oslo-incubator
form of syncing common functionality.

The package, apiclient, was moved to a top level location
and a new i18n module was created. There is no oslo.apiclient
library or equivalent, the recommended solution is to move it
in tree and maintain it there.

Change-Id: Ia788313e0926dc872a87b090ef0a350898bfb079