On Mon, Jul 15, 2019 at 4:36 AM Ehigie Aito <[email protected]> wrote:
> Like I said, in older versions of Django, that variable used to be named > MIDDLEWARE_CLASSES, if I create a Django project with Python 3.7 and Django > 2.2.3, its MIDDLEWARE but Python 3.8 and Django 2.2.3 its named > MIDDLEWARE_CLASSES which on running python manage.py runserver fails. Here > is the traceback: > This seems very unlikely. Here is the default settings file Django 2.2.3 will create: https://github.com/django/django/blob/2.2.3/django/conf/project_template/project_name/settings.py-tpl#L42 It contains MIDDLEWARE. It does not contain MIDDLEWARE_CLASSES. Are you 100% completely certain that: * You do not have an older version of Django that might have been used to generate the settings file, and * You are not using any sort of custom project template that hasn't been updated to use the MIDDLEWARE setting? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAL13Cg-H8H%2B7gUTaxp1zMBnG_7%3DLfycDSGCHDsFVmSm0SuhRXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
