openstack/designate-dashboard
Code Issues Proposed changes

translation: drop babel extractor definitions

Browse Source 
babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.

This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.

Change-Id: Id90a29feed0bae697168492ac43961535178fe85
This commit is contained in:
Akihiro Motoki 2019-12-27 02:01:04 +09:00
parent 9d15e3f4a3
commit b7ce98f169
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
babel-django.cfg
View File

@ -1,5 +1,2 @@
[extractors]
django = django_babel.extract:extract_django
[python: **.py] [python: **.py]
[django: **/templates/**.html] [django: **/templates/**.html]