Move all Django Evolution settings into a DJANGO_EVOLUTION dictionary.
Review Request #12218 — Created March 30, 2022 and submitted — Latest diff uploaded
In an effort to better namespace Django Evolution settings and keep them
manageable, this change introduces a newsettings.DJANGO_EVOLUTION
dictionary. Currently, this supportsCUSTOM_EVOLUTIONS
andENABLED
keys, but will later include aCUSTOM_MIGRATIONS
setting.The old
settings.DJANGO_EVOLUTION_ENABLED
andsettings.CUSTOM_EVOLUTIONS
are still supported, but will emit a deprecation warning.All settings are now accessed through a new
django_evolution.conf.django_evolution_settings
object, which is an
instance ofDjangoEvolutionSettings
. This manages loading settings (both
modern and legacy), defaults, and responding to Django'ssettings_changed
signal.
Unit tests pass on all versions of Django and Python.
Manually tested the values by tweaking Django settings and running management
commands.
Diff Revision 1
This is not the most recent revision of the diff. The latest diff is revision 2. See what's changed.
Commits
Files
django_evolution/conf.py |
---|
django_evolution/management/__init__.py |
---|
django_evolution/management/commands/evolve.py |
---|
django_evolution/management/commands/migrate.py |
---|
django_evolution/management/commands/syncdb.py |
---|
django_evolution/tests/test_conf.py |
---|
django_evolution/tests/test_evolution_utils.py |
---|
django_evolution/utils/evolutions.py |
---|
docs/coderef/index.rst |
---|