#21750: STATIC_ROOT is required in 1.7
-------------------------------------+------------------------------------
     Reporter:  aaugustin            |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  contrib.staticfiles  |                  Version:  1.6
     Severity:  Release blocker      |               Resolution:
     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 mjtamlyn):

 The existing patch to #21581 seems to be a major inconvenience to me, and
 is certainly unreleasable on 1.6.x. - we can't make projects which run (or
 test suites which run) suddenly start breaking. I certainly have projects
 where the `STORAGE_BACKEND` is deliberately configured different during
 the tests (and sometimes even for local dev) to avoid the possibility of
 overwriting the files on S3.

 It seems reasonable that `collectstatic` should do the check, but should
 do so by asking the `STORAGE_BACKEND` whether it is properly configured
 before running the command - thus not leaking the implementation details.

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

Reply via email to