#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
-------------------------------------+------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"7e27885c6e7588471fd94a4def16b7081577bdfc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e27885c6e7588471fd94a4def16b7081577bdfc"
 Reworked the detection of local storages for the collectstatic command.

 Before 4befb30 the detection was broken because we used isinstance
 against a LazyObject rather than against a Storage class. That commit
 fixed it by looking directly at the object wrapped by LazyObject.
 This could however be a problem to anyone who subclasses the
 collectstatic management Command and directly supplies a Storage class.

 Refs #21581.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21581#comment:12>
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.dc4e246cf3740c7dfbf88f322a7f94e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to