#29776: Pulling part of django.conf.settings from the database
-----------------------------------+--------------------------------------
Reporter: Sven R. Kunze | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: settings database | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Carlton Gibson):
Searching mailing list for “dynamic settings” returns
[https://groups.google.com/forum/#!searchin/django-
developers/dynamic$20settings%7Csort:date a long list of historical
discussions] of this sort of suggestion. (Including dynamic app plugins
and everything else.)
At this point I think it’s fair to say it’s been considered, and rejected
as not feasible or worth the complications.
To push it forward I think it would require a proof-of-concept in the form
of a working thrid-party application. That those that have been attempted
in the past are abandoned—if that’s true across the board—should tell us
something. If you’re able to pick one up and make it work then a post to
django-developers discussing whether it could be brought into core would
be reasonable.
--
Ticket URL: <https://code.djangoproject.com/ticket/29776#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.e503844089d2a1cb49917d583a540ebb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
