Package: python3-django Version: 3:4.2.20-1 Severity: wishlist X-Debbugs-Cc: sal...@pytower.com
Dear Maintainers, The default Python 3 version on Debian Trixie is set to be 3.13, while Django 4.2 is currently planned for inclusion. The issue is that, according to the official Django documentation, Django 4.2 is only supported on Python versions 3.8, 3.9, 3.10, 3.11, and 3.12 (with 3.12 being added in version 4.2.8) [1]. Additionally, the end-of-life (EOL) for Django 4.2 does not align with the EOL for Debian Trixie, which could result in a short support lifespan for Django 4.2 within this release. Therefore, would it be possible to package Django 5.2 in Debian Trixie instead of Django 4.2? [1] https://docs.djangoproject.com/en/dev/faq/install/#faq-python-version- support -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.20-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-django depends on: ii python3 3.13.2-2 ii python3-asgiref 3.8.1-1 ii python3-sqlparse 0.5.3-1 Versions of packages python3-django recommends: ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 ii python3-tz 2025.1-3 Versions of packages python3-django suggests: pn bpython3 <none> pn geoip-database-contrib <none> ii gettext 0.23.1-1 pn ipython3 <none> pn libgdal20 <none> pn libsqlite3-mod-spatialite <none> pn python-django-doc <none> ii python3-bcrypt 4.2.0-2.1+b1 pn python3-flup <none> pn python3-memcache <none> ii python3-mysqldb 1.4.6-2+b5 pn python3-pil <none> pn python3-psycopg2 <none> pn python3-selenium <none> pn python3-sqlite <none> pn python3-yaml <none> -- no debconf information
