Ok, before I start let me apologize. It seems I am the proverbial boy who cried wolf as I have discovered where the source of the problem. I hope my explanation will help anyone who might make the mistake I was making. Lets start: On my development machine, I had Django 1.9.5 installed globally and in Django 1.9.5, in the settings.py file, now MIDDLEWARE is called MIDDLEWARE_CLASSES. Somehow in new Django projects I was creating with Python 3.8 in a virtualenvironment, calling django-admin to create it, Python 3.8 wasnt using the django-admin command of the installed Django in the virtual environment but was using that of the globally installed version 1.9.5 which has MIDDLEWARE_CLASSES and on completion, trying to run the project with Python 3.8 caused it to fail. This never happens with Python 3.7 though as it always uses the django-admin of the virtual environment.
Hope my apology is accepted. Thank you all very much for your help. Kind regards On Monday, July 15, 2019 at 1:25:24 PM UTC+1, Curtis Maloney wrote: > > > > 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, <[email protected] > <javascript:>> 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 [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > 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 > > <https://groups.google.com/d/msgid/django-developers/5a40defe-8a9c-46cc-b2f1-5cf4fea652b8%40www.fastmail.com?utm_medium=email&utm_source=footer> > . > 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 [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > 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 > > <https://groups.google.com/d/msgid/django-developers/CA%2BB1BD4atpnwQWiJBEYzGpc5orLcxj8%3DiMU1Y-kc%3DomAfELBZA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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 [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/1b216c6b-d40e-4756-9dc6-1dea38242091%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
