Package: python3-jinja2 Version: 3.0.3-1 Severity: normal Currently python3-jinja2 depends on python3-babel. Jinja2 is used in cloud-init and is pulling in data of almost 30MB corresponding to almost 5% of the size of a Debian cloud image.
The babel module is not once loaded in the code. The only occurance of it is the integration of Jinja2 into babel as extractor. Due to it not being used at all, please make it at most Recommends. Bastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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-jinja2 depends on: ii python3 3.10.6-1 ii python3-babel 2.8.0+dfsg.1-7 ii python3-markupsafe 2.0.1-2+b2 Versions of packages python3-jinja2 recommends: ii python3-pkg-resources 59.6.0-1.2 Versions of packages python3-jinja2 suggests: pn python-jinja2-doc <none> -- no debconf information
