Re: Django 1.7 problem

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUf61dAAoJEC0ft5FqUuEhpbkQAKQh2orgR28sZPFjJLSKOOLg
KlFOuRLAQo/SUUCSXDmmNJuCCd/9RHLc2syBdvroYak3sadx5jp2fXccvIHZEFMF
4//x/rpHBeGc+obVkLSTLPUM3FgXYfYngNrsPOM3o93dtOgukM4aJjmH2HgKwTcI
bsOxnWF/ckFfhrc83+mJMrDVIHqG8s3lAdfEVNKCp00NCWnTgDa7sRpVSmdK0D7F
6waqYlJxEu+WC3pCilVVSJEytA0nEK87h2faYuTZI4TpWhtArTmwArULZjzY++LK
dprzBqu/+Bk/LjKTUPCXgWPXxsXA0JmkIwoUZd+N4rIH1ukdN44Fcu7Yo8g7Llwn
dpOQ/RlG3rbrfjaSTd4DUXzbcKyz+rS/H/CpR5Fbe2EEtKfKIov7Zomfn/51Bv6c
CerW6vSgyeO0TIlpCawW9wP5vbhNw0jLviLAoOGt0ym5mOFsogzj56nUMwnxMIzx
BRr1WPH2x4mwCxxSH9XHHj2pJ64rnvyzTxm2N4TALEGTz8eEvW7PeBw39ghAj3q2
lZmXVu/6vmuCFgtkypVR9Kz+b9O7zSPRR7YvtSCI7YM6K+l4f6CBq38E29wrfgxq
yAgd4U06dnZA5CXOJ6k5q444d5JUZkfs61mQ0S/sSr8y/6kaVggrSBpTZ15OL3BD
gxPRzxCStNqZlCbA3JDu
=vt79
-----END PGP SIGNATURE-----
Hi Andreas,

On 12/03/2014 01:34 PM, Andreas Kuhne wrote:
> I am trying to migrate our current website to django 1.7.
>
> Currently we are using a plugin called django-dbgettext to get parts of our
> database translated (we are running in 10 different languages). The problem
> is that django-dbgettext starts by going through all of the models and does
> this before the translation framework is running. So I get an exception
> during startup that says:
> "django.core.exceptions.AppRegistryNotReady: The translation infrastructure
> cannot be initialized before the apps registry is ready. Check that you
> don't make non-lazy gettext calls at import time."
>
> The problem seems to be that the classes are loaded before the models are
> correctly loaded and the translation framework is running. All of the
> classes use ugettext_lazy, but the stack trace includes ugettext.
>
> I want to rewrite the django-dbgettext plugin so that it goes through the
> code AFTER the models are correctly loaded. I don't know how to do this
> however. Is there anyway of running code after django is fully initialized?

Indeed there is! See
https://docs.djangoproject.com/en/dev/ref/applications/#django.apps.AppConfig.ready

> Django admin should do the same thing, it also has a autodiscover()
> function and I was wondering why this doesn't happen with django admin?
> Could this be a good place to start looking for a solution?

Yes, admin.autodiscover now runs in the admin's AppConfig.ready() in
Django 1.7, so that would have been a good place to start looking :-)

Carl

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/547FAD59.5090809%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.