#24452: Staticfiles backends using HashedFilesMixin don't update CSS files' hash
when referenced media changes
-------------------------------------+-------------------------------------
     Reporter:  Paul McLanahan       |                    Owner:  Paul
                                     |  McLanahan
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.staticfiles  |                  Version:  1.7
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by David Sanders):

 Replying to [comment:21 Tim Graham]:
 > Meanwhile, we have to live with all the extra static files?

 Living with broken static files that referred to incorrect files was a bit
 more of an inconvenience than some extra files lying around, but it
 managed to hang around for quite a while. There's already 2N static files
 since the original non-hashed file is always kept, with the extra
 intermediate files it's 2N + M and in most cases M is going to be a dozen
 or two compared to N being likely a couple hundred or more.

 > Could you write to the DevelopersMailingList to propose the deprecation
 and explain the current situation?

 I really can't, I don't have the time to shepherd the issue. I can chime
 in from time to time though. I will add that it'd be nice to consider a
 manifest option where the manifest was inserted into the codebase like
 `locale` translations rather than relying on the manifest file being
 stored with the static files.

--
Ticket URL: <https://code.djangoproject.com/ticket/24452#comment:22>
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/068.feda928a0bd0580c1630e1ae1f3bb37d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to