Gary Kotton 994ddd79c7 LOG.warn -> LOG.warning ...

Python 3 deprecated the logger.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning
so we prefer to use warning to avoid DeprecationWarning.

In addition to this there will be a hacking rule to prevent this
(https://review.openstack.org/#/c/262257/)

TrivialFix

Change-Id: Iec8499951cd10a910a4d8ecdac95f5bb53a2e86e

2015-12-31 01:58:10 -08:00

..

__init__.py

Use the correct _ from vmware_nsx._i18n file

2015-12-06 07:04:17 -08:00

base.py

LOG.warn -> LOG.warning

2015-12-31 01:58:10 -08:00

client.py

Switch to internal _i18n pattern, as per oslo_i18n guidelines

2015-12-02 06:59:23 -08:00

eventlet_client.py

Switch to internal _i18n pattern, as per oslo_i18n guidelines

2015-12-02 06:59:23 -08:00

eventlet_request.py

LOG.warn -> LOG.warning

2015-12-31 01:58:10 -08:00

exception.py

Use the correct _ from vmware_nsx._i18n file

2015-12-06 07:04:17 -08:00

request.py

LOG.warn -> LOG.warning

2015-12-31 01:58:10 -08:00

version.py

Switch to internal _i18n pattern, as per oslo_i18n guidelines

2015-12-02 06:59:23 -08:00