#27929: Add an option when collecting statics to remove non-cached files after
processing
-------------------------------------+------------------------------------
Reporter: Jesse | Owner: nobody
Type: New feature | Status: new
Component: contrib.staticfiles | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by Ed Morley):
* cc: Ed Morley (added)
Comment:
I agree an option to remove the original files would be great.
Replying to [comment:1 Tim Graham]:
> I think it's okay, see ticket:24452#comment:17 and subsequent comments
for possibly related discussion.
So I think those comments were more about the intermediate files left
behind (eg `foo.<intermediate-hash>.css`) rather than the original files
(eg `foo.css`). For fixing the former there's ticket #28604, which would
likely do the right thing all the time, rather than being opt-in. However
I guess the same `CachedStaticFilesStorage` limitation might apply to the
original files too.
That said, given this feature would be opt-in, and could perhaps be made
to only support `ManifestStaticFilesStorage`, then perhaps this feature
could be added even before #28606 / #28604?
Fwiw, WhiteNoise rolls its own implementation to remove them currently:
https://github.com/evansd/whitenoise/blob/9d3ad51f7f05e5391ec6f2f03211d958a08e374f/whitenoise/storage.py#L32
...though I'm likely going to be revising it slightly to be more like:
https://github.com/moccu/barbeque/blob/dc714b4fa7ce2ad517a0d37474f8a774df46219c/barbeque/staticfiles/storage.py#L16-L17
--
Ticket URL: <https://code.djangoproject.com/ticket/27929#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.e952b9eb9a500616a99eab6c7af2f5bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
