Re: Python 3.8 and Django 2.2.3 Issues

No need to apologise ... we're all human - we can (and do) all make mistakes. More importantly - we all learned :) I believe this is why James was trying to verify which Django (and where) you were really invoking. Problems like this are why a lot of people recommend against installing any Pyt

Re: Python 3.8 and Django 2.2.3 Issues

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

Re: Python 3.8 and Django 2.2.3 Issues

I've just created empty project with Python 3.8.0b1 and Django 2.2.3 everything works properly. -- 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

Re: Python 3.8 and Django 2.2.3 Issues

Do we try to investigate or just wait till the final version of Python 3.8 gets released? My knowledge of the inner workings of Django isn't that deep enough to be able to pinpoint what exactly is causing this for me. On Mon, 15 Jul 2019, 13:25 Curtis Maloney, wrote: > > > On Mon, 15 Jul 2019, a

Re: Python 3.8 and Django 2.2.3 Issues

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.8

Re: Python 3.8 and Django 2.2.3 Issues

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, wrote: > I think you're making an assumption about the cause of the problem, > without evidence

Re: Python 3.8 and Django 2.2.3 Issues

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 cha

Re: Python 3.8 and Django 2.2.3 Issues

I actually thought pipenv was the issue, and used virtualenv to create my django project with Python 3.8 and Django 2.2.3. In the settings file, its still named as MIDDLEWARE_CLASSES instead of MIDDLEWARE and trying to run the project makes it fail On Monday, July 15, 2019 at 12:53:51 PM UTC+1,

Re: Python 3.8 and Django 2.2.3 Issues

I actually thought pipenv was the issue, and used virtualenv to create my django project with Python 3.8 and Django 2.2.3. In the settings file, its still named as MIDDLEWARE_CLASSES instead of MIDDLEWARE and trying to run the project makes it fail On Monday, July 15, 2019 at 12:53:51 PM UTC+1,

Re: Python 3.8 and Django 2.2.3 Issues

This is the contents of the file generated when I use Python 3.7.3 and Django 2.2.3 from django.utils.version import get_version VERSION = (2, 2, 3, 'final', 0) __version__ = get_version(VERSION) def setup(set_prefix=True): """ Configure the settings (this happens as a side effect of

Re: Python 3.8 and Django 2.2.3 Issues

This is part of the settings file generated when I create a project with Python 3.7.3 and Django 2.2.3 MIDDLEWARE = [ 'django.middleware.security.SecurityMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.midd

Re: Python 3.8 and Django 2.2.3 Issues

On Mon, Jul 15, 2019 at 4:41 AM Ehigie Aito wrote: > Not at all, I create all new Django projects from scratch and with pipenv. > This only happens with Python 3.8.0 b1 > Open a Python interpreter and type this: import django print(django.VERSION) print(django.__file__) Make sure VERSION retur

Re: Python 3.8 and Django 2.2.3 Issues

On Mon, 15 Jul 2019, at 21:36, Ehigie Aito 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

Re: Python 3.8 and Django 2.2.3 Issues

Not at all, I create all new Django projects from scratch and with pipenv. This only happens with Python 3.8.0 b1 On Mon, Jul 15, 2019 at 12:39 PM James Bennett wrote: > On Mon, Jul 15, 2019 at 4:36 AM Ehigie Aito wrote: > >> Like I said, in older versions of Django, that variable used to be na

Re: Python 3.8 and Django 2.2.3 Issues

On Mon, Jul 15, 2019 at 4:36 AM Ehigie Aito 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

Re: Python 3.8 and Django 2.2.3 Issues

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 trac

Re: Python 3.8 and Django 2.2.3 Issues

On Mon, 15 Jul 2019, at 21:23, Curtis Maloney wrote: > First for everyone reading, it's important to note that Python 3.8 hasn't > been released yet. To elaborate on this point - it's _close_ to release, so it's valuable to see how Django behaves with it. -- C -- You received this message bec

Re: Python 3.8 and Django 2.2.3 Issues

First for everyone reading, it's important to note that Python 3.8 hasn't been released yet. Secondly, a new project in current Django will not emit "MIDDLWARE_CLASSES" in a new settings file. Could you explain how you determined something had "changed" the setting? Could you also provide deta

Python 3.8 and Django 2.2.3 Issues

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