Hi Moritz! On Fri, Oct 16, 2020 at 08:04:56PM +0200, Moritz Mühlenhoff wrote: > There will be few core packages build-depending on Python 2 (for tests > or building) which won't be ready for Python 3 for Bullseye (Chromium, > qtwebkit and IIRC also Pypy), but those only need Python 2 (and a very > small set of support packages like setuptools/jinja) to build and > run their tests.
Small correction: s/qtwebkit/qtwebengine/. QtWebEngine bundles Chromium whose upstream is actively working on Python 3 port [1]. Most probably it won't be ready in time for Bullseye, but for Bookworm it should be ready (or rather, Qt WebEngine 6 will use Python 3, and we will remove Qt WebEngine 5). There are also patches from the FreeBSD maintainer [2], but they are huge (2200 lines in total) and the author reports that they cause some JS errors, so I would better not apply them and wait for an official port. Qt WebEngine in Debian is not supported from security point of view anyway, so I think it should be fine to let it use Python 2 in Bullseye. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1112471 [2]: https://mail.kde.org/pipermail/distributions/2020-September/000860.html -- Dmitry Shachnev
signature.asc
Description: PGP signature
