DATABASES = {
'default': {
'ENGINE': 'sql_server.pyodbc',
'NAME': 'dbName',
'USER': 'userName',
'PASSWORD': 'password',
'HOST':'hostName',
'PORT': 1433,
'OPTIONS': {
'driver': "SQL Server"
}
}
}
I had to downgrade to : pip install 'django-pyodbc-azure<1.11' which was
otherwise giving me a error of No Server/DSN found. However after
downgrading when I execute "python manage.py makemigrations" or python
manage.py runserver.
Following is my error, which I am unable to understand. Any help would be
of great help.
Thanks in advance.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
(venv) C:\Users\L_Sharma\PycharmProjects\Test1>python manage.py
makemigrations
Traceback (most recent call last):
File "manage.py", line 21, in <module>
main()
File "manage.py", line 17, in main
execute_from_command_line(sys.argv)
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\core\management\__init__.py", line 367, in
execute_from_command_line
utility.execute()
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\core\management\__init__.py", line 341, in execute
django.setup()
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\apps\registry.py", line 108, in populate
app_config.import_models(all_models)
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\apps\config.py", line 199, in import_models
self.models_module = import_module(models_module_name)
File
"C:\Users\L_Sharma\AppData\Local\Programs\Python\Python38-32\lib\importlib\__init__.py",
line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 975, in
_find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 783, in exec_module
File "<frozen importlib._bootstrap>", line 219, in
_call_with_frames_removed
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\contrib\auth\models.py", line 4, in <module>
from django.contrib.auth.base_user import AbstractBaseUser,
BaseUserManager
File "C:\Users\L_Sharma\PycharmProjects\Test1\venv\lib\site-
packages\django\contrib\auth\base_user.py", line 52, in <module>
class AbstractBaseUser(models.Model):
RuntimeError: __class__ not set defining 'AbstractBaseUser' as <class
'django.contrib.auth.base_user.AbstractBaseUser'>. Was __classcell__
propagated to type.__new__?
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
--
Ticket URL: <https://code.djangoproject.com/ticket/31374>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => invalid
Old description:
New description:
--
Comment:
First of all `django-pyodbc-azure < 1.11` is not compatible with Django
3.0, secondly it's a 3rd-party package so it's not an issue in Django
itself, and finally, please don't use trac as a support channel.
--
Ticket URL: <https://code.djangoproject.com/ticket/31374#comment:1>
Comment (by Andrew Badr):
Commenting in case this helps anyone else. I hit this same error trying to
upgrade a simple Django 1.9.13 project from python 2.7 to python 3.8.
`RuntimeError: __class__ not set defining 'AbstractBaseUser' as <class
'django.contrib.auth.base_user.AbstractBaseUser'>. Was __classcell__
propagated to type.__new__?`
Not using `django-pyodbc-azure` or anything else unusual. This error seems
be coming from within Django itself.(File
"/app/.heroku/python/lib/python3.8/site-
packages/django/contrib/auth/base_user.py", line 49). What's strange is
that the error doesn't happen for my locally, only on Heroku.
Upgrading to Django 1.11 fixed the issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/31374#comment:2>