Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

[Thomas Goirand <zigo@debian.org>]

Hi,

In some cases I've seen, particularly in the med or science team,
switching some packages to Python 3 requires a significant effort.

For example, today I looked into removing Python 2 from python-cogent.
Running sixer on all files lead to a huge log of problems to solve by
hand. There's no upstream support for Python 3 on that one.

For this kind of package, I see no way out except:
- Upstream works on Python 3 support
- Someone in Debian makes the effort

But in both cases, it's going to take a very long time. Do we really
want to get stuck on these packages for like forever, or would it feel
ok to raise the severity to serious, so that the package gets
auto-removed and then we can work on removing Python 2 from its
dependencies?

Cheers,

Thomas Goirand (zigo)