From b7ce98f169d3e36c55a596dc0c27396203a78418 Mon Sep 17 00:00:00 2001 From: Akihiro Motoki Date: Fri, 27 Dec 2019 02:01:04 +0900 Subject: [PATCH] translation: drop babel extractor definitions 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 --- babel-django.cfg | 3 --- 1 file changed, 3 deletions(-) diff --git a/babel-django.cfg b/babel-django.cfg index e78d6c0..9a8ac3b 100644 --- a/babel-django.cfg +++ b/babel-django.cfg @@ -1,5 +1,2 @@ -[extractors] -django = django_babel.extract:extract_django - [python: **.py] [django: **/templates/**.html]