Hi, On Jul 15, 2013, at 9:22 AM, Carl Meyer <[email protected]> wrote:
> On 07/14/2013 07:16 AM, Jannis Leidel wrote: >> Yeah, I can relate to that, it does to me, too. I think decoupling >> the file serving slightly from how the files got to the place they >> are served from, is a good first step. The common denominator between >> the core ability to serve files and staticfiles is the reliance on >> conventions like STATIC_ROOT and STATIC_URL. If we can backscale >> LiveServerTestCase to only do the core ability out of the box and >> document the way to do it the staticfiles way, then I think we're on >> the right track. > > This advice makes a lot of sense to me. I think we should be able to > make the staticfiles integration pretty easy; i.e. just have a subclass > of LiveServerTestCase that lives in django.contrib.staticfiles that > adjusts the behavior to use the full staticfiles finders, where the base > LiveServerTestCase in core just serves from STATIC_ROOT. I think that's a great idea. This way, all you'd need to do to have the full static finders is make your TestCase inherit from that subclass, and there would be no need to ever run collectstatic while running your tests. Julien -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
