Comment 0 for bug 1820182

[Availability]

Package is in universe.

Builds for python 2 and 3, but we only need python3-django-filters.

[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:

Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.

django-filter is used by python3-djangorestframework

[Security]

No known CVEs found.

[Quality assurance]

As part of the mailman3 stacks as of now (Disco) this installs fine and works fine.
On itself it is useful to (many) other dependencies and does not need a post install configuration on its own.

Package does not ask debconf questions.

Launchpad bugs (0): https://bugs.launchpad.net/ubuntu/+source/django-filter

Debian bugs (0): https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=django-filter

Upstream issues: https://github.com/carltongibson/django-filter/issues

No significant bugs.

Package seems well maintained at https://tracker.debian.org/pkg/django-filter

Package does not depend on exotic hardware.

Package does not ship a test suite.

Package has a watch file.

No significant lintian issues.

Package does not rely on obsolete or about to be demoted packages.

[UI standards]

Not an end user application

[Dependencies]

Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.

[Standards compliance]

Package follows standard python install practices.

[Maintenance]

The Server team will subscribe for the package for maintenance, but in
general it seems low on updates and currently is a sync from Debian.

[Background]

Good package description.