Open Stack

I am aware of the issue.

While switching to enmerkar looks like the straightforward way,
I am trying to explore a way to continue django-babel to minimize the
impact to consumers and packagers.

When we switch enmerkar, we need to clean up babel-django.cfg in horizon [1]
and all horizon plugin repos, plus the infra manual. babel-django.cfg specifies
an extractor from django-babel explicitly. We need to drop the extract
entry first
(as the "django" extractor is registered via an entrypoint in the
recent django-babel
and enmerkar).

BTW, how did you notice this?

[1] https://opendev.org/openstack/horizon/src/branch/master/babel-django.cfg



On Sun, Dec 22, 2019 at 6:28 AM Matthew Thode <mthode at mthode.org> wrote:
>
> it looks like django-babel is unmaintained since 2017, so perhaps it's
> time to look for a replacement.  Looking through github issues, it looks
> like enmerkar is a possible replacement.  If that's fine with horizon /
> django consumers we can start by adding enmerkar to global-requirements
> and upper-constraints.
>
> Thanks,
>
> --
> Matthew Thode