Opened 12 months ago

Last modified 8 months ago

#28606 new Cleanup/optimization

Deprecate CachedStaticFilesStorage

Reported by: Ed Morley Owned by: nobody
Component: contrib.staticfiles Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


CachedStaticFilesStorage has a number of drawbacks, and the docs in fact already steer people away from using it:

An additional problem is that HashedFilesMixin has had to make several compromises in order to support CachedStaticFilesStorage which unfortunately also impacts users of the recommended ManifestStaticFilesStorage backend (see #28604). When these compromises were added in #24452, it was suggested that CachedStaticFilesStorage should just be deprecated/removed instead.

It's now too late to mark it as deprecated for Django 2.0, but we can do so for Django 2.1 which would end up with its removal being in Django 3.0 all the same anyway.

I started this mailing list thread about the deprecation:!topic/django-developers/fmfQvuHBStk

Change History (1)

comment:1 Changed 12 months ago by Tim Graham

Summary: Mark CachedStaticFilesStorage as deprecated in Django 2.1Deprecate CachedStaticFilesStorage
Triage Stage: UnreviewedAccepted
Note: See TracTickets for help on using tickets.
Back to Top