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
Use lazy translation to avoid import issues #1012
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This isn't blocking me, so no rush. Also, it wasn't causing me a real issue except as a distraction because it looks like a big failure. I don't plan on testing that this resolves the issue until the fix comes through on master.
👍 sounds good. I'll merge once tests pass, but won't make a new ORA release just for this. |
Understood. Thanks. |
@efischer19 FYI - the issue that was fixed by this PR is causing a stack trace during LMS (and other) testing on my devstack. Here's the full error:
Any idea when the next ORA2 release containing this fix will happen? |
@doctoryes I've been noticing that as well - I can just go ahead and push out a release tomorrow, it won't take too much effort. I think there's going to be a similar release made for the similar "is not from an app in INSTALLED_APPS" warnings, but that fix is more non-trivial than this. |
Thanks. In Django 1.9, the code is not allowed to import models before the "application was loaded". The warnings are likely caused by that condition and will need a deeper fix. |
@robrap, I believe this will fix the issues you pinged me about. Can you review when you get a chance?
If you need this to go out soon I can do an ORA release after we merge this in