Marking as RB till we know how we want to handle ot.
--
Ticket URL: <https://code.djangoproject.com/ticket/27033>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
New description:
Marking as RB till we know how we want to handle it. Do we have a way to
check if the app is installed without triggering app registry ready
checks?
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27033#comment:1>
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>
Comment (by timgraham):
I think the use case of the project is obsoleted by the commit that caused
the regression: cf546e11ac76c8dec527e39ff8ce8249a195ab42 allows form
`Media` to use staticfiles automatically without having to call `static()`
on each file. If we have to add a release note about this, I suggest
something like "`django.templatetags.static.static()` now raises
`AppRegistryNotReady` if called at application loading time." I think it's
likely to be a rare issue and probably wouldn't happen in django-easy-
select2 if convenience imports weren't provided in the project's
`__init__.py`.
--
Ticket URL: <https://code.djangoproject.com/ticket/27033#comment:3>
* status: new => closed
* resolution: => wontfix
Comment:
Seems legit, just wanted another opinion :D
--
Ticket URL: <https://code.djangoproject.com/ticket/27033#comment:4>