[Openstack-i18n] [openstack-dev] [nova][i18n] Is there any point in using _() inpython-novaclient?

Steve Martinelli stevemar at ca.ibm.com
Sun Sep 6 05:18:25 UTC 2015

Isn't this just a matter of setting up novaclient for translation? IIRC
using _() is harmless if there's no translation bits set up for the


Steve Martinelli
OpenStack Keystone Core

From:	Matt Riedemann <mriedem at linux.vnet.ibm.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>,
            openstack-i18n at lists.openstack.org
Date:	2015/09/04 01:50 PM
Subject:	[openstack-dev] [nova][i18n] Is there any point in using _() in

I noticed this today:


And it got me thinking about something I've wondered before - why do we
even use _() in python-novaclient?  It doesn't have any .po files for
babel message translation, it has no babel config, there is nothing in
setup.cfg about extracting messages and compiling them into .mo's, there
is nothing on Transifex for python-novaclient, etc.

Is there a way to change your locale and get translated output in nova
CLIs?  I didn't find anything in docs from a quick google search.

Comparing to python-openstackclient, that does have a babel config and
some locale po files in tree, at least for de and zh_TW.

So if this doesn't work in python-novaclient, do we need any of the i18n
code in there?  It doesn't really hurt, but it seems pointless to push
changes for it or try to keep user-facing messages in mind in the code.



Matt Riedemann

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20150906/053740bd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20150906/053740bd/attachment-0001.gif>

More information about the Openstack-i18n mailing list