Bug#942953: debian-timeline: Python2 removal in sid/bullseye
Tags: sid bullseye
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
Please stop using Python2, and fix this issue by one of the following
- Convert your Package to Python3. This is the preferred option. In
case you are providing a Python module foo, please consider dropping
the python-foo package, and only build a python3-foo package. Please
don't drop Python2 modules, which still have reverse dependencies,
just document them.
This is the preferred option.
- If the package is dead upstream, cannot be converted or maintained
in Debian, it should be removed from the distribution. If the
package still has reverse dependencies, raise the severity to
"serious" and document the reverse dependencies with the BTS affects
command. If the package has no reverse dependencies, confirm that
the package can be removed, reassign this issue to ftp.debian.org,
make sure that the bug priority is set to normal and retitle the
issue to "RM: PKG -- removal triggered by the Python2 removal".
- If the package has still many users (popcon >= 300), or is needed to
build another package which cannot be removed, document that by
adding the "py2keep" user tag (not replacing the py2remove tag),
using the firstname.lastname@example.org user. Also any
dependencies on an unversioned python package (python, python-dev)
must not be used, same with the python shebang. These have to be
replaced by python2/python2.7 dependencies and shebang.
This is the least preferred option.
If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the email@example.com mailing list.