Hi Carlton,
1. I apologize for the time taking me to reply. I had other things to
handle before I could handle this issue.
2. The settings in models such as User are per class/model and not per
instance. You can see the models in the following file:
Hi Uri.
Does it work if you make `User.settings` a property, that fetches the
values dynamically, rather than assigning them once at import time?
Something like:
@property
def settings(self):
return django_settings.USER_SETTINGS
--
You received this message because you are subscribed
tests in the
shell will run them.
Note: ENV_MIN_SLUG_LENGTH could be any name. This is only for demonstration
purposes, OK?
Shalom!
On Mon, 31 Dec 2018 at 02:07, אורי wrote:
>
> https://stackoverflow.com/questions/53953444/overriding-settings-in-django-when-used-by-the-models
I don't understand why is it relevant to my question? It's not what I asked.
אורי
u...@speedy.net
On Mon, Dec 31, 2018 at 3:12 PM Jason wrote:
> Sounds like what you want is something in
> https://djangopackages.org/grids/g/live-setting/
>
> This will let you change settings via an admin
Sounds like what you want is something in
https://djangopackages.org/grids/g/live-setting/
This will let you change settings via an admin interface
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop
https://stackoverflow.com/questions/53953444/overriding-settings-in-django-when-used-by-the-models
We are using Django for Speedy Net and Speedy Match
<https://github.com/speedy-net/speedy-net> (currently Django 1.11.17, we
can't upgrade to a newer version of Django because of one
6 matches
Mail list logo
