John Vandenberg

Using mock brought in its own problems. I tried your pytest-stub which looked interesting, but didnt get that working for this app settings scenario. Also tried a few other over-complicated...

The specific case was I had a test case which was using `django.conf.settings` for a variable that was previously unnecessarily project wide. I had moved it into `.settings` when implementing...

The 'cause' for this was the 'need' to import the toolbox into `/settings.py`, which is very early in the Django startup. That could be avoided in other ways. However, I...

Ya, I would like that approach, to avoid lots of unneeded attempts at imports.

Ya, my WIP needs "only on demand" added. It is only a POC to get the ball rolling.

Prefs of all install apps automatically added to Django admin; is that asking too much ? ;-)

I read the code, got a bit excited as I could see it was intended to be doing this, but getting it working is a bit challenging. I expected that...

> So basically you want the same outcome as if thirdparty apps support siteprefs out-of-box. I expect it wont be as good, and may not work at all, but rudimentary...

Correct. It already has the basic functionality, working with redis, but a bit buggy so hard to demo. https://github.com/baranbartu/onthefly#screenshot . I havent tried the file backend available in the pulls....

The 'proper' way to do project wide settings still mystify me a little However https://github.com/idlesign/django-siteprefs/pull/24 means I can include the `VAR=val` and pref UI definitions in my `/settings.py` . I...