collectstatic's output of `skipping x (not modified)` isn't very clear

[Keryn Knight]

Running manage.py collectstatic gives output like:

Skipping 'img/hello.jpg' (not modified)

Based on that message, it's unclear why the file was skipped. Is it because the contents are the same? A hash collision of the filename, content? Permissions? etc.

It's actually just because the timestamps match, ​as far as I can tell based on a quick ​search, which is absolutely fine, but I had to go to the implementation to find out what constituted it being unmodified.

I'd like to suggest that the wording be improved/clarified. Perhaps just something like modified dates are the same (I'm not tied to that wording specifically!).

[AMaini503]

--> Modified the message as required for more clarity

Line 267 : collectstatic.py (old)

 self.log("Skipping '%s' (not modified)" % path)

Line 267-269 : collecstatic.py (new)

# Message changed to convey the reason clearly as to why the file was skipped beca
# Compares timestamps using --> http_date
self.log("Skipping '%s' (Dates of last modification are same)" % path)

[Claude Paroz]

As far as I'm concerned, (not modified) seems rather clear (the file has not been modified since last run). I don't find the proposal better.

[Tim Graham]

I agree with Claude.