On Mon, Jan 27, 2014 at 12:52 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> I wanted to write to the mailing list about this problem. Thanks for
> bringing it up.
>
> Here's what happens. Django 1.7 is more strict about the import sequence.
> Technically, the app registry pop
I wanted to write to the mailing list about this problem. Thanks for bringing
it up.
Here’s what happens. Django 1.7 is more strict about the import sequence.
Technically, the app registry population process isn't re-entrant anymore. As a
consequence, it isn’t possible to call get_user_model()
On 11:39 Sun 26 Jan , Marcin Szamotulski wrote:
> Hello,
>
> I ask the question here since it is about the developed Django-1.7
> version but if you think that I should ask it at django-users then
> please excuse me.
>
> When I use get_user_model in a top level of another app models I got an
Hello,
I ask the question here since it is about the developed Django-1.7
version but if you think that I should ask it at django-users then
please excuse me.
When I use get_user_model in a top level of another app models I got an
error :
>>> django.setup()
File "", line 1, in
File
