#25689: Merge staticfiles into core
--------------------------------------+--------------------
Reporter: collinanderson | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
(James Aylett on stage at duth)
If you accidentally use {% load static %} instead of {% load staticfiles
%} you won't take advantage of storage engines. However, 3rd-party apps
won't know if the staticfiles library is installed or not.
One solution he mentioned is having {% load static %} match the behavior
of {% load admin_static %} (where it uses staticfiles only if it's
installed), but that would probably involve core importing code from
contrib (usually a no-no).
Another option he gave was merging staticfiles into core. He thought it
might be contentious, but I think is actually a better idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/25689>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/057.97ef855b36f47f7e0a4b3d29423332e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
