The fact it provides a tag of the same name as the "correct" tag from
`staticfiles` doesn't help either.
Could it be deprecated?
(And if I wanted to follow up with an accompanying PR, should I be using
`RemovedIn110Warning` or `RemovedIn20Warning` (the latter of which has
several instances, but surprises me slightly)
--
Ticket URL: <https://code.djangoproject.com/ticket/24192>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Ok, `RemovedIn20Warning`, thanks apollo13
--
Ticket URL: <https://code.djangoproject.com/ticket/24192#comment:1>
Comment (by doismellburning):
Ah, I've just noticed this is used by admin; this PR is getting more fun!
--
Ticket URL: <https://code.djangoproject.com/ticket/24192#comment:2>
Comment (by doismellburning):
So `django.contrib.admin.templatetags.admin_static` tries to use
`django.contrib.staticfiles.templatetags.staticfiles` if the app's there,
otherwise falls back to `django.templatetags.static`.
Can anyone provide guidance as to "improved" behaviour there please? Is
there any kind of policy against apps from contrib depending on one
another? Is it reasonable for `d.c.admin` to assume/require
`d.c.staticfiles`? If the latter, can anyone point me to an existing
example so I can crib from its mechanisms please?
--
Ticket URL: <https://code.djangoproject.com/ticket/24192#comment:3>
* cc: julian@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/24192#comment:4>
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Core (Other)
Comment:
I don't see much advantage here vs. the pain this is likely to cause
(force everyone to use `contrib.staticfiles` and `{% load static %}` in
their templates. The documentation points users in the direction IMO.
There has been some talk of "if we did it again, static files might have
been better in core, rather than contrib", but I'm not sure if that's
something that's worth changing at this point. See also #18942. Feel free
to raise the issue on the DevelopersMailingList or reopen if you think
I've missed something here.
--
Ticket URL: <https://code.djangoproject.com/ticket/24192#comment:5>