• Python 2 removal in sid/bullseye: Progress and next steps

    From =?UTF-8?Q?Ond=C5=99ej_Nov=C3=BD?=@21:1/5 to All on Mon Nov 11 10:40:02 2019
    Hi,

    We are aiming to remove Python 2 for the bullseye release, or at least
    remove as many Python 2 related packages as possible. Python 2 is
    discontinued upstream, but crucially, more and more providers of Python
    modules don't support Python 2 in either the current or future upstream version.

    Some FAQs and guidelines can be found at https://wiki.debian.org/Python/2Removal.

    With about 3300 py2removal bugs filed and 1500 closed, we are now
    almost done with half of the removals.

    We are going to raise the severity of the py2removal bugs to "serious"
    in several steps. In the
    first phase we are going to raise severity of the py2removal bugs for
    all leaf module packages and low popcon (< 300) application packages.
    Bugs marked with the "py2keep" user tag will not have their severity
    raised. If nobody fixes that bug, the packages will be auto-removed
    from testing.
    We will also then file bug reports against ftp.debian.org to remove
    such packages from unstable. We are going to do this semi-
    automatically as additional packages become leaf packages.

    We are working with the Lintian maintainers to bump the severity of
    Python 2 related tags in Lintian.

    If you are absolutely sure you need to keep your Python 2 only
    application
    in Debian, you should mark the Python 2 removal bug with the "py2keep"
    user tag
    (please do not replace the py2remove tag), using the debian-python@lists.debian.org user.
    Please CC the bug report, because it's non-obvious who is changing a
    user tag by just reading the bug report, and provide a rationale for
    claiming it is "py2keep".
    py2keep must not be placed on reverse dependencies of pygtk, because
    the Debian Gnome maintainers already announced the removal of pygtk in bullseye.

    All dependency fields in debian/control and debian/tests/control must
    also be updated to stop using the unversioned python
    packages (python, python-dbg, python-dev, python-doc) and instead use
    the versioned package names (python2,
    python2-dbg, python2-dev, python2-doc); this applies to both build-time
    and runtime dependencies.
    Unversioned interpreters must also not be used in the shebang lines
    (use
    #!/usr/bin/python2 instead). When using dh-python, this will be done automatically. Check for explicit python and python-dev build
    dependencies. Don't forget to look at autopkgtest tests as well (for
    both package and interpreter names).

    For questions, feel free to contact people on the debian-python@lists.debian.org ML or on IRC (#debian-python on OFTC).

    --
    Best regards
    Ondřej Nový
    Matthias Klose


    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl3JKvMACgkQNXMSVZ0e BkudZA//bkhgXdB1si6qYrKFqlHKwhtzq1ZCRATHd36kxgScv/KtdZr+1Is3kwmL pQBqMl+OEIEVbMEi0UK94SMMDVvV2S329W9TLfKBQJwwLSlEdxNbWbeIoMzgvEOw ApQI4TrMoX26W78mhEsOWc1etPmfopDm+3lqUjY6dVGlZy0QcFP9PtgvMVDfyceV Np0QRbdE+iSTZnfhkrmUA+Jq1ZqTYxPbtw6PWqe3SS3+Ci79bQxu4cSTEq6TZSOA DQjBh+FMr1aRrH2foUx+4A9T1LgYijfXaXItNzAMXBlGMzjKGbbOL+cFzGSJruL6 vOmka1HlHIN2RSazdiFLIA0X0GQgbvFZSu34f0SVDI8XR7jKQ5bU2z3cQS+Qf0dS ODKA19JzHZ4Jdk7LSZuZrm05UcQNxLfwosAqg9Lac988NTc1eQAdhAPhxHgswc8o PZAd3wv0dq2AHjZetB988pYvstzKmkAOI+gIZlUu9s1RefA9UkfQx21P/XT5F3eq 6XnXbY3hebOVWt9+2bILVLttp6pw8nLd2IE2NP33ZAk1G7k2fia53Ib1H3pxEfXH jNKL8LW7ZrQBlYHS8ylx49K0q8gC4DZbiZyjTtKYEnt6sg+DwTwclW5FJqliKeYz /+TzeQDtEYfxVpI9vXjEtGgCZ6OGRtmB/OlcstkSElB1t7pijwc=
    =Mt7c
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)