swift .pot files not being generated in setup.py build

[Jay Pipes]

Not sure how nobody noticed this (perhaps no i18n users of Swift..), but the i18n build hasn't worked, and the translations branch I setup for Swift bexar release was deleted.

Anyway, the setup.py needs to be updated to properly use DistUtilsExtra, which bypasses problems in the babel library's integration with setuptools.

After this is done, Swift's automatic import/export of the translation templates needs to be set up again on Launchpad.

[Thierry Carrez (ttx)]

Not release-critical since there are no translations anyway...

[Monty Taylor (mordred)]

Actually- I'm working on moving nova and glance back to babel... when I do, I'll go back into swift and make sure that we get this working.

[Chmouel Boudjnah (chmouel)]

it's been one year is i18n still something we should support? I am not sure what's the openstack policy as well on this.

[Clark Boylan (cboylan)]

The process for making this work is to add swift as a project under the OpenStack umbrella on transifex, give the openstackjenkins user account admin right to push .pot files to transifex, add the translation-jobs to swift, and run the swift-upstream-translation-update as part of the zuul post queue.

Additionally the python setup.py Babel commands should work for swift as we rely on them in the Jenkins jobs.

I won't have time to immediately do this and Daisy will be given more transifex powers so we might have her do this as part of her learning process. In any case feel free to ping me if people want a walk through on how to make this happen sooner rather than later.