Re: contrib.staticfiles and runserver

On Oct 28, 9:45 pm, SmileyChris wrote: > My suggestion is that StaticFilesHandler only does its magic if > 'django.contrib.staticfiles' is found in INSTALLED_APPS. Does that > sound acceptable? That seems like a very reasonable opt-in approach that solves the

Re: contrib.staticfiles and runserver

On Fri, Oct 29, 2010 at 9:45 AM, SmileyChris wrote: > It's cool that runserver takes away the hassle of needing to add in > your static url (is this documented? I didn't find it in my skim) but > doing it by default seems pretty backwards incompatible, even if we > are just

Re: contrib.staticfiles and runserver

On Oct 29, 2:45 pm, SmileyChris wrote: > doing it by default seems pretty backwards incompatible, even if we I was a bit terse, let me expand. STATICFILES_URL defaults to '/static/'. The StaticFilesHandler (which is now what is used by runserver) swallows requests to this

contrib.staticfiles and runserver

It's cool that runserver takes away the hassle of needing to add in your static url (is this documented? I didn't find it in my skim) but doing it by default seems pretty backwards incompatible, even if we are just talking about the dev server. My suggestion is that StaticFilesHandler only does