[Python-modules-team] Bug#972626: python3-mysqldb: backporting python3-mysqldb not to break backported python3-django

[Salman Mohammadi]

Package: python3-mysqldb
Version: 1.3.10-2
Severity: wishlist

Dear Maintainer(s),

I would kindly ask if it is possible to backport python3-mysqldb from
Bullseye to Buster-backports not break the backported python3-django.

The backported version of python3-django has this line

Breaks: ... , python3-mysqldb (<< 1.3.13)

which could be solved by backporting python3-mysqldb.

Regards,
Salman

-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-mysqldb depends on:
ii libc6 2.28-10
ii libmariadb3 1:10.3.25-0+deb10u1
ii libssl1.1 1.1.1d-0+deb10u3
ii python3 3.7.3-1
ii zlib1g 1:1.2.11.dfsg-1

python3-mysqldb recommends no packages.

Versions of packages python3-mysqldb suggests:
pn default-mysql-server | virtual-mysql-server <none>
pn python-egenix-mxdatetime <none>
pn python3-mysqldb-dbg <none>

-- no debconf information