#27033: static tag causes AppRegistryNotReady errors on 1.10
-------------------------------------+------------------------------------
Reporter: apollo13 | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.staticfiles | Version: 1.10
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by claudep):
Seems like the more recent easy_select2 doesn't suffer from this any more
(https://github.com/asyncee/django-easy-select2/commit/8b9a4f050166).
If we really want to be able to use `static()` before/during app
population we could catch the exception and return some lazy object. Not
sure about that.
At a minimum, release notes should be updated.
--
Ticket URL: <https://code.djangoproject.com/ticket/27033#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.809e3a861d5fd303dbe4c55953f550c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
