#21581: collecstatic --clear is too lax about warning users
-------------------------------------+------------------------------------
Reporter: loic84 | Owner: loic84
Type: Bug | Status: closed
Component: contrib.staticfiles | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4befb3015c26810a68cfcf57e0cd8b062f56f1c5"]:
{{{
#!CommitTicketReference repository=""
revision="4befb3015c26810a68cfcf57e0cd8b062f56f1c5"
Fixed #21581 -- Fixed a number of issues with collectstatic.
When STATIC_ROOT wasn't set, collectstatic --clear would delete
every files within the current directory and its descendants.
This patch makes the following changes:
Prevent collectstatic from running if STATIC_ROOT isn't set.
Fixed an issue that prevented collectstatic from displaying the
destination directory.
Changed the warning header to notify when the command is run
in dry-run mode.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21581#comment:5>
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/064.3ee2ec6e7d7bb2faabf61a8989bf5abf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
