Deprecation of "DEFAULT_FILE_STORAGE" - Can we easen the migration?

[adamchainz]

@timgraham

Disallowing something so generic as LOGOUT_URL will cause unneeded annoyance. Third-party code sometimes reimplements functionality like this. Now we would suddenly break things for them.

I don’t see this as a big issue. Any third-party packages “recycling” names are adding unnecessary confusion for their users who may search for that setting name and find old Django docs and blog posts.

IMO package settings should be prefixed with their package name.

@timgraham

Although the proposed check could be disabled, usage of one disallowed setting requires disabling the check completely in order to silence the warning.

We have a ticket to silence checks with more granularity: #26472 (Allow finer granularity in the ability to silence checks) – Django . Admittedly, it will still be easier to silence a check outright, but at least it will be more at the user’s disrgression.