Creating a project with Python 3.8 and Django 2.2.3, the MIDDLEWARE variable in the (link: http://settings.py) settings.py file is changed to MIDDLEWARE_CLASSES which makes running this command: '(link: http://manage.py) manage.py runserver' fail. Can anyone kindly try to reproduce this error?
--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 django-develop...@googlegroups.com.To post to this group, send email to django-d...@googlegroups.com.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/2b4a4bf0-1fec-43b6-8c8e-88569eb57e45%40googlegroups.com.For more options, visit https://groups.google.com/d/optout.
First for everyone reading, it's important to note that Python 3.8 hasn't been released yet.
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/fc05ecd2-41a0-4326-9fe9-f3a80128c49f%40www.fastmail.com.
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:
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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.
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:
Exception in thread django-main-thread:Traceback (most recent call last):File "/usr/local/lib/python3.8/threading.py", line 923, in _bootstrap_innerself.run()File "/usr/local/lib/python3.8/threading.py", line 865, in runself._target(*self._args, **self._kwargs)File "/home/pystar/.local/share/virtualenvs/del-wUbba1cG/lib/python3.8/site-packages/django/utils/autoreload.py", line 54, in wrapperfn(*args, **kwargs)File "/home/pystar/.local/share/virtualenvs/del-wUbba1cG/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 117, in inner_runself.check(display_num_errors=True)File "/home/pystar/.local/share/virtualenvs/del-wUbba1cG/lib/python3.8/site-packages/django/core/management/base.py", line 436, in checkraise SystemCheckError(msg)django.core.management.base.SystemCheckError: SystemCheckError: System check identified some issues:ERRORS:?: (admin.E408) 'django.contrib.auth.middleware.AuthenticationMiddleware' must be in MIDDLEWARE in order to use the admin application.?: (admin.E409) 'django.contrib.messages.middleware.MessageMiddleware' must be in MIDDLEWARE in order to use the admin application.?: (admin.E410) 'django.contrib.sessions.middleware.SessionMiddleware' must be in MIDDLEWARE in order to use the admin application.
Not at all, I create all new Django projects from scratch and with pipenv. This only happens with Python 3.8.0 b1
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/5a40defe-8a9c-46cc-b2f1-5cf4fea652b8%40www.fastmail.com.
Like I said, I didn't say the problem was from Django. I said it's from Python 3.8 because creating a project with Python 3.7 doesn't produce this traceback.
On Mon, 15 Jul 2019, 13:07 Curtis Maloney, <cur...@tinbrain.net> wrote:I think you're making an assumption about the cause of the problem, without evidence.Yes, there's an issue shown in that traceback related to middleware, but I've not seen yet why you've concluded it's creating a settings.py with MIDDLEWARE_CLASSES.I think the problem is more likely some change in Python 3.8 is making the middleware not initialise, or the detection of what's in the MIDDLEWARE list is not working.Can you elaborate on what evidence you have that the combination of Python 3.8 and Django 2.2.3 is generating a settings.py with MIDDLEWARE_CLASSES ?--C
--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 django-develop...@googlegroups.com.To post to this group, send email to django-d...@googlegroups.com.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/5a40defe-8a9c-46cc-b2f1-5cf4fea652b8%40www.fastmail.com.For more options, visit https://groups.google.com/d/optout.
--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 django-develop...@googlegroups.com.To post to this group, send email to django-d...@googlegroups.com.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/CA%2BB1BD4atpnwQWiJBEYzGpc5orLcxj8%3DiMU1Y-kc%3DomAfELBZA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4f1ba28c-97e3-465d-bf5a-235fbcedf501%40www.fastmail.com.
On Mon, 15 Jul 2019, at 22:13, Ehigie Aito wrote:Like I said, I didn't say the problem was from Django. I said it's from Python 3.8 because creating a project with Python 3.7 doesn't produce this traceback.I think it's quite clear there is an incompatibility with Django and Python 3.8a1.I just don't think it's your original conclusion of "Creating a project with Python 3.8 and Django 2.2.3, the MIDDLEWARE variable in the settings.py file is changed to MIDDLEWARE_CLASSES"
I'm trying to ask for what _evidence_ you have that this change has happened.
As I said earlier, I think there is a change in how Python 3.8 works that is causing those checks to fail.--C
On Mon, 15 Jul 2019, 13:07 Curtis Maloney, <cur...@tinbrain.net> wrote:
I think you're making an assumption about the cause of the problem, without evidence.Yes, there's an issue shown in that traceback related to middleware, but I've not seen yet why you've concluded it's creating a settings.py with MIDDLEWARE_CLASSES.I think the problem is more likely some change in Python 3.8 is making the middleware not initialise, or the detection of what's in the MIDDLEWARE list is not working.Can you elaborate on what evidence you have that the combination of Python 3.8 and Django 2.2.3 is generating a settings.py with MIDDLEWARE_CLASSES ?--C
--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 django-d...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.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/5a40defe-8a9c-46cc-b2f1-5cf4fea652b8%40www.fastmail.com.For more options, visit https://groups.google.com/d/optout.
--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 django-d...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.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/1b216c6b-d40e-4756-9dc6-1dea38242091%40googlegroups.com.