#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 Sym Roe):
I'm picking up on this issue as I've found the existing behaviour to be
problematic. When using the `static` template tag, it's far too easy for a
typo to be introduced that is hard to spot in development, but causes a
500 for the whole page in production.
I think this contrast between `DEBUG` being `True` or `False` is too
great, when in most cases Django should try to serve the page even if a
single asset can't be served for whatever reason.
I understand this is tagged as `wontfix`, but I wonder if a PR with the
above `file_exists_strict` flag would be acceptable? I'm happy to adapt
the above code and open a new PR if so.
--
Ticket URL: <https://code.djangoproject.com/ticket/31520#comment:13>
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/01070182f336c281-5f07764c-531a-491d-927d-bccd976e2f7b-000000%40eu-central-1.amazonses.com.
