Igor Starikov

Maybe we should support a more granular way. ``` PREFS_MODULE_NAMES = { '*': 'settings, 'otherapp': 'apssettings', } ``` or something. Need to think it over.

Messing with `django.conf.settings` can be disastrous. Need to be very careful, and to apply patching only on demand.

`MANAGE_SAFE_COMMANDS` was a dirty workaround for something indeed. Will try to recall for what in more detail, when came back after the weekends.

API is a very special topic. No one size fits all solution seems possible. Maybe we could offer some primitives (yet I don't known what those may be), but only...

Hi. Thank you. And what exact features do you want to see?

Hm. But autodiscovery is already handled out of the box. ``SITEPREFS_MODULE_NAME`` setting is taken from project's ``settings.py`` and all apps are seatched for settings module (defaults to ``settings.py``). On may...

`autodicover` is triggered by default in https://github.com/idlesign/django-siteprefs/blob/master/siteprefs/config.py#L19 There should be no need for explicit discovery in recent Django versions. `if 'self' not in settings_locals` is meant for project wide settings,...

> Already done ;) https://github.com/baranbartu/onthefly/pulls/jayvdb Hm. I can there only two PR's: 5 and 6. One about ordering and the other is on serialization. And that obviously is not what...

> Hooray! Congratulations! > The 'proper' way to do project wide settings still mystify me a little Yeah, it might be. The thing is there are at least two project...

Yeah, creating required tables is a must. That's described in: https://django-siteprefs.readthedocs.io/en/latest/quickstart.html Personally I don't bother with pytest-django and use ``pytest-djangoapp`` instead.