To have the decision revisited, you should raise it on django-developers.
On Monday, March 23, 2015 at 10:39:57 AM UTC-4, Ben Scherrey wrote:
>
> Hey Tim,
>
>Appreciate the link. It looks like we're trying to have it go both ways
> here. If we don't want to allow it into production then make
Hey Tim,
Appreciate the link. It looks like we're trying to have it go both ways
here. If we don't want to allow it into production then make it explicit
and break it - just as before. If we want to recommend that it not go into
production but then let users actually do it, don't silently break
Please see https://github.com/django/django/commit/4c6ffcf7 for the
rationale for the change. I am open to ideas, but I'm concerned that
including details about the reason for the 404 might cause information
leakage in production which wouldn't be desirable.
On Monday, March 23, 2015 at 10:06:2
I see now that the behaviour of serve() was changed for 1.7 and it now
returns a silent misleading 404 result rather than the old
ImproperlyConfigured exception which would have provided a clue as to the
actual root cause.
See:
https://docs.djangoproject.com/en/1.7/ref/contrib/staticfiles/#django.
Can someone explain the test condition on line 31 of
https://github.com/django/django/blob/master/django/contrib/staticfiles/views.py
- Just spent a few hours trying to get my unit tests to pass and couldn't
figure out what was going on until I found this weirdness.
I understand serve() isn't mean
5 matches
Mail list logo
