Creating migrations in Django 1.7 introspects that field definition and adds the choices iterable of a CharField into the migration. This causes an issue for fields like the form_selection field in the FormBlock because it is configured in the settings.
We need to make the current settings available to the migration via a function call or generated constant at runtime.
Creating migrations in Django 1.7 introspects that field definition and adds the
choicesiterable of aCharFieldinto the migration. This causes an issue for fields like theform_selectionfield in theFormBlockbecause it is configured in the settings.We need to make the current settings available to the migration via a function call or generated constant at runtime.