tkaemming/wat — comment on commit 46c855dc41ae96eb9a863eb1fec7dcf70c33fc79
File:  line 0
By tkaemming:

hi jannis — thanks for the reply. sorry if it came across earlier as i was just throwing code over the wall and asking you to debug my issue for me, because that certainly wasn't my intent — it was more just confusion about the implementation and how i had anticipated it working. my (incorrect) assumption was that leading-slashed urls in the static files would be resolved relative to the root of the storage, which is probably out of context a reasonable assumption, but in context doesn't really work for the reasons you noted. (maybe this is a place where a more explicit error or at least an admonition in the documentation about the method in which urls are resolved would be helpful? if you have any thoughts on how to handle this, i'd love to contribute a patch to make it clearer to others in the future because this was a major stumbling point for me, obviously.)

the point about not being able to bind the mixin to `STATIC_URL` makes 100% sense after you brought it up and would be a bad implementation overall to contribute back to core in hindsight. sorry about the confusion there — i should of looked into the implementation details before i suggested a change.

thanks again for the comments — i've otherwise really been happy working with the new cached files mixin (implementation with s3 boto storage has been a breeze, other than this issue and the other one i patched), and i think they're a great aid to what has already been very helpful with the staticfiles app.