Open Stack

A heads up and a request for advise:

Babel 2.3.3 release broke extraction of log level messages from strings
and extracted instead of e.g. "_LW" the default "_". So, the proposal
job removed all content for that. Fortunately, Zanata will keep the
strings, so once an upload with a fixed Babel happens, this should be
fine again.

See https://review.openstack.org/#/c/304985/ for one example - the error
manifests with all pot files having exactly the same content.

But I wanted to be safe and since babel 2.3.2 broke horizon and now
2.3.3 breaks python projects, I have - as teemporary measure - disabled
translation sync completely to buy us time to evaluate what to do.


There's a requirements change to update versions (blocking all broken
babel releases): https://review.openstack.org/#/c/305000

Upstream bug report https://github.com/python-babel/babel/issues/388

And one way of working around it the bug is not using "python setup.py"
but "pybabel" directly for python projects - like we do for django
already. This needs testing and review - and some updates (see review
comment): https://review.openstack.org/305043

We can also wait for Babel 2.3.4 release - and test first that it works
as desired.

Advise on which way to go forward as well as testing and review of
305043 are welcome!

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126