Change Details

Debian Bullseye comes with Python 3.9, so we're going to need support for it in CI (example: https://gerrit.wikimedia.org/r/c/labs/codesearch/+/713729). Currently we only support up to Python 3.8 via https://people.debian.org/~paravoid/python-all/ Presumably we can have a bullseye container that just runs tox with 3.9 for now until the python-all backports are available.

Debian Bullseye comes with Python 3.9, so we're going to need support for it in CI (example: https://gerrit.wikimedia.org/r/c/labs/codesearch/+/713729). Currently we only support up to Python 3.8 via https://people.debian.org/~paravoid/python-all/ Presumably we can have a bullseye container that just runs tox with 3.9 for now until the python-all backports are available. Python versions provided by Debian: | Distro | Python version |--|-- | Stretch | 3.4 | Buster | 3.7 | Bullseye | 3.9 Our CI images: | Image | Distro | Pythons |--|--|-- | releng/tox | Stretch | 3.4 **3.5** 3.6 3.7 | releng/tox-buster | Buster | 3.5 3.6 **3.7** 3.8 If we move CI to Buster we loose 3.4 which might not be an issue. We can either: - backport 3.9 to Buster - build 3.5, 3.6, 3.7, 3.8 for Bullseye Or drop support for python 3.4, 3.5 and 3.6 entirely and get the new minimum supported version to be 3.7 shipped by Buster but there bunch of repositories still relying on python 3.5 / Stretch.

Debian Bullseye comes with Python 3.9, so we're going to need support for it in CI (example: https://gerrit.wikimedia.org/r/c/labs/codesearch/+/713729). Currently we only support up to Python 3.8 via https://people.debian.org/~paravoid/python-all/ Presumably we can have a bullseye container that just runs tox with 3.9 for now until the python-all backports are available. Python versions provided by Debian: | Distro | Python version |--|-- | Stretch | 3.4 | Buster | 3.7 | Bullseye | 3.9 Our CI images: | Image | Distro | Pythons |--|--|-- | releng/tox | Stretch | 3.4 **3.5** 3.6 3.7 | releng/tox-buster | Buster | 3.5 3.6 **3.7** 3.8 If we move CI to Buster we loose 3.4 which might not be an issue. We can either: - backport 3.9 to Buster - build 3.5, 3.6, 3.7, 3.8 for Bullseye Or drop support for python 3.4, 3.5 and 3.6 entirely and get the new minimum supported version to be 3.7 shipped by Buster but there bunch of repositories still relying on python 3.5 / Stretch.