#11663: Delete orphaned replaced files
---------------------------------------------+------------------------------
Reporter: SmileyChris | Owner: SmileyChris
Status: closed | Milestone:
Component: File uploads/storage | Version: SVN
Resolution: wontfix | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by mtredinnick):
For the record (since I just got a Trac collision whilst also wontfix'ing
this), my logic is: Django shouldn't be in the business of deleting files,
which is more of a system-level task. We have no way of knowing what else
on the system is using those files. If we *don't* delete a file and the
user wants to remove it, they can use the os module. If we *do* delete a
file and that wasn't the right thing (from the point of view of something
else on the system), the user is screwed. We cannot guarantee that removal
is correct, so we shouldn't do it.
Writing a utility function to check for orphaned files and clean them up
is a simple enough operation. Whether to include it in Django or not is
debateable (it's kind of like the cleanup sessions management command, I
guess) and the topic for another ticket. Doing it automatically feels too
dangerous to be correct at any time.
--
Ticket URL: <http://code.djangoproject.com/ticket/11663#comment:14>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
