This fixes #28
Collect all settings in
Thanks bigtime to @Fantomas42 for the approach used in django-blog-zinnia for loading custom models.
After trying to implement this and playing around with various proxy and abstract models, I've concluded that it's not possible to implement this without renaming either the model which to access (the one proxying for custom settings) or renaming/moving the default database table and its accessor model (because otherwise it will name collide with the proxy model).
To put it shortly, we can't have a concrete model
If we want to use
So what I came up with is to not reinvent the wheel and instead opt for this:
Because Django's swappable API is considered undocumented and subject to change (although it hasn't changed for quite some time), it's probably safer to go through an application that implements whatever Django uses internally.
Closing this and trying a new PR with swapper instead...
Just another quick update: I'm still working on this. It looks possible!
However, as with