#23724: Overwrite mode in django
-------------------------------------+-------------------------------------
Reporter: prathik | Owner: nobody
Type: New feature | Status: closed
Component: contrib.staticfiles | Version: 1.7
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
Has patch: 1 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
I don't think Django can track which static files it manages. Consider an
app that has some of its static files removed from its app directory.
Django would then have to consider the copies of those files that remain
in `STATIC_ROOT` as "unmanaged" and they would never be deleted.
I think the warnings I linked to in my previous comment should be enough
for people to see that files in their app's static directory will be
deleted if they proceed.
I'm going to close this ticket as "won't fix" as the idea of an "overwrite
option" goes against one of the design decisions of static files. If you
wish to argue for a design decision, could you please start a thread on
the DevelopersMailingList? Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/23724#comment:7>
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/065.4458ea21b56e7999b2c70d3127d8ef74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
