#31520: ManifestStaticFilesStorage should not raise ValueError on missing file
when
manifest_strict=False
-------------------------------------+-------------------------------------
Reporter: thenewguy | Owner: thenewguy
Type: New feature | Status: closed
Component: contrib.staticfiles | Version: 3.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by thenewguy):
Replying to [comment:10 Carlton Gibson]:
Hi Carlton,
Would you merge if this was behind a feature flag as you suggested?
A 500 error makes debugging difficult when templates can be updated
outside of the main code release process - for example, tenant specific
templates. The template developer typically does not have access to the
traceback in this case. A 404 is easy to debug with a browser console but
a 500 error doesn't give any detail to correct the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/31520#comment:11>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.0a83a6821b82ad51e52d1f870e0352fa%40djangoproject.com.
