On Sun, Aug 17, 2014 at 9:24 AM, Jay Bryant <jsbry...@electronicjungle.net>
wrote:

> +2
>
> I prefer the LOG.warning format and support that given the documentation
> you shared.
>
> If there is agreement I would create a hacking check.
>

I think a better approach is to just not care which i used here. IMHO
mixing up LOG.warn and LOG.warning doesn't hurt readability in any
meaningful way. And not caring will result in less churn for very little
benefit.


>  Jay
> On Aug 17, 2014 1:28 AM, "Gary Kotton" <gkot...@vmware.com> wrote:
>
>>  Hi,
>> Over the last few weeks I have seen a number of patches where LOG.warn is
>> replacing LOG.warning. I think that if we do something it should be the
>> opposite as warning is the documented one in python 2 and 3
>> https://docs.python.org/3/howto/logging.html.
>> Any thoughts?
>> Thanks
>> Gary
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to