Discrepancy about staticfiles finders strategy

[Claude Paroz]

Tutorial 6 says:
Django will choose the first static file it finds whose name matches
​https://docs.djangoproject.com/en/dev/intro/tutorial06/#customize-your-app-s-look-and-feel

Static files howto says:
Django will use the last static file it finds whose name matches
​https://docs.djangoproject.com/en/dev/howto/static-files/#configuring-static-files

Documentation for STATICFILES_FINDERS could also tell something about this strategy.
​https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#staticfiles-finders

[Baptiste Mispelon]

The tutorial is the correct one.

It's consistent with the template loaders mechanism: Django goes through each loader and if a match is found, it returns it.

Each loader is then free to implement its own logic, but the default ones work on a "first match returned" basis:

• FileSystemFinder goes through each directory in settings.STATICFILES_DIR (in order) and returns the first match.
• AppDirectoriesFinder goes through each app in settings.INSTALLED_APPS (in order) and return the first match too.

The collectstatic command will also only handle the first match. That is, if it finds a static file whose name has already been handled, it skips it.

[Tim Graham <timograham@…>]

In 9be93aa809c34083ebef8392e52c83df0e383be3:

Fixed #20634 - Corrected doc mistake re: staticfiles finders strategy.

Thanks claudep for the catch and bmispelon for the research.

[Tim Graham <timograham@…>]

In 519fdacf5127540638f7c1b4a3656d9a31f16a8b:

Fixed #20634 - Corrected doc mistake re: staticfiles finders strategy.

Thanks claudep for the catch and bmispelon for the research.

Backport of 9be93aa809 from master.

[Jannis Leidel]

This may have been introduced during the last staticfiles docs refactor in February. :-/