#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:"1e9e7351f88a59261da6e616934c8283a6e3e565"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1e9e7351f88a59261da6e616934c8283a6e3e565"
 Fixed #21750 -- Fixed regression introduced by 4befb30.

 Validating STATIC_ROOT in StaticFilesStorage.__init__ turned out to be
 problematic - especially with tests - because the storage refuses to work
 even
 if there are no actual interactions with the file system, which is
 backward
 incompatible.

 Originally the validation happened in the StaticFilesStorage.path method,
 but
 that didn't work as expected because the call to
 FileSystemStorage.__init__
 replaced the empty value by a valid path. The new approach is to move back
 the
 check to the StaticFilesStorage.path method, but ensure that the location
 attribute remains None after the call to super.

 Refs #21581.
 }}}

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

Reply via email to