New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppRegistryNotReady exception #144
Comments
Try upgrading to the latest django-watson. https://github.com/etianen/django-watson/blob/master/CHANGELOG.markdown On Sun, 13 Dec 2015 at 16:55, tsebire notifications@github.com wrote:
|
I already did, that's why I don't know what can I do next. I'll retry tonight and keep you updated. |
Hmm, do you have a full traceback that I can investigate? On Mon, 14 Dec 2015 at 09:00 tsebire notifications@github.com wrote:
|
Here you go : Traceback (most recent call last): |
I fixed the problem by putting the watson import in the ready method of AppConfig and not at the beginning of my file (it was working like this before). Thanks for your time. |
@tsebire thanks for posting your fix. I'd been looking at this for about 2 hours now! |
Out of interest, what causes the exception? It is running buildwatson, or I'm confused, because none of the unit tests pick up on this. On Sun, 3 Jan 2016 at 23:39 fresh-django notifications@github.com wrote:
|
It was thrown on runserver command. |
I'd like to keep this open for now. It should be possible to import watson at the top-level of your apps.py file. I'm not sure right now why it's not... |
Ok my bad :). Good luck fixing this and happy new year. |
I'm also seeing this with Django 1.9.1:
Throws: |
What worked for me is to move "from watson import search as watson" into the ready() function. No idea what's going on behind the scene though. |
Check out the latest master branch. This should be fixed. |
Keeping this issue open for now, until confirmation that it's fixed... |
@Athemis moving into ready() worked for me. |
@etianen I tried it with the latest master branch. Unfortunately it still gives the same error: |
Can I have the full traceback? |
|
Oh, the ContentTypes framework. Gotcha. Try the latest master now. On Mon, 29 Feb 2016 at 15:03 TommySprat notifications@github.com wrote:
|
I had the same issue but the issue RESOLVED as per Dave's advice to use the latest master branch. Thanks for the hard work. |
Cool, I'll release on Monday! :D
|
I also tried that latest master branch and can confirm that it's fixed on my system too. |
This is now released as 1.2.1 |
Hello,
I can't register a model in watson anymore since I've upgraded to Django 1.9.
It raises a AppRegistryNotReady exception. I'm using an AppConfig for my module set in my init.py file :
When I comment the watson import and the register line, I don't have any error.
Am I missing something ?
The text was updated successfully, but these errors were encountered: