django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module. Did you install mysqlclie

最新推荐文章于 2025-04-14 11:15:30 发布

搬砖小胖子

最新推荐文章于 2025-04-14 11:15:30 发布

阅读量1.1k

点赞数

分类专栏： Django 文章标签： django

本文链接：https://blog.youkuaiyun.com/qq_39567748/article/details/106962135

版权

Django 专栏收录该内容

1 篇文章

订阅专栏

本文详细介绍了如何解决Django项目中使用PyMySQL作为数据库驱动时遇到的兼容性问题，包括安装配置、错误排查及修复步骤。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

解决办法：
1、pycharm安装pymysql

2、在项目原始目录中编辑init.py文件（与settings.py相同）。加：
import pymysql
pymysql.install_as_MySQLdb()

3、再次运行报错如下：
 File "/Users/ptmind/Documents/Sublime_file/python3/newfile/djang3/venv/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 37, in <module>
    raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__)
django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 0.9.3.

4、根据报错看到37行
vim /Users/ptmind/Documents/Sublime_file/python3/newfile/djang3/venv/lib/python3.7/site-packages/django/db/backends/mysql/base.py
到37行
注释掉以下几行
#if version < (1, 3, 13):
#    raise ImproperlyConfigured('mysqlclient 1.3.13 or newer is required; you have %s.' % Database.__version__)

5、再次运行你会看到
python3 manage.py migrate
System check identified some issues:

WARNINGS:
?: (mysql.W002) MySQL Strict Mode is not set for database connection 'default'
        HINT: MySQL's Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/3.0/ref/databases/#mysql-sql-mode
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, rongkang, sessions
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying admin.0003_logentry_add_action_flag_choices... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying auth.0009_alter_user_last_name_max_length... OK
  Applying auth.0010_alter_group_name_max_length... OK
  Applying auth.0011_update_proxy_permissions... OK
  Applying rongkang.0001_initial... OK
  Applying sessions.0001_initial... OK

python3 manage.py runserver
Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
June 25, 2020 - 19:53:08
Django version 3.0.7, using settings 'djangotest.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.