Spilt settings in dataclass and Django settings proxy

[jaap3]

Simplify the configuration a bit by decoupling the defaults from Django settings lookup / legacy setting handling.

[adamchainz]

No thanks. This isn’t simpler as it requires understanding data classes and __getattribute__, which is famously hard to implement correctly (I don’t think it is correct here).

[jaap3]

@adamchainz too bad, I probably should've clarified my motivations. I'm looking into some way to apply CORS settings to specific views (via decorator, or other ways), with the possibility of differing settings per view. One of the things that's making that harder is the global nature of the configuration. This was an initial attempt of making it possible to configure things in "other ways" (i.e. by passing it as an argument somewhere).

Would be nice to know what you think is incorrect about the __getattribute__ implementation.