[Python-modules-team] Bug#931592: python3-django: should suggest python3-mysqldb >= 1.3.13
Zhang Jingqiang
zh_jq at outlook.com
Mon Jul 8 04:03:21 BST 2019
Package: python3-django
Version: 2:2.2.3-2
Severity: important
Dear Maintainer,
After upgrading to django 2.2.3-2, I get the following while starting
myapp:
django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 1.3.10.
It will be good if we can conflict with python3-mysqldb < 1.3.13.
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-django depends on:
ii dpkg 1.19.7
ii python3 3.7.3-1
ii python3-sqlparse 0.2.4-1
ii python3-tz 2019.1-1
Versions of packages python3-django recommends:
ii libjs-jquery 3.3.1~dfsg-3
Versions of packages python3-django suggests:
pn bpython3 <none>
pn geoip-database-contrib <none>
pn gettext <none>
pn ipython3 <none>
pn libgdal20 <none>
pn libsqlite3-mod-spatialite <none>
pn python-django-doc <none>
ii python3-bcrypt 3.1.6-1
pn python3-flup <none>
pn python3-memcache <none>
ii python3-mysqldb 1.3.10-2
pn python3-pil <none>
pn python3-psycopg2 <none>
pn python3-sqlite <none>
ii python3-yaml 3.13-2
-- no debconf information
More information about the Python-modules-team
mailing list