Hey Hugo, > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > > > - 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. > > Upstream is currently working on the migration. As far as I am aware, we > should > not be too far from a final Python 3 release. I have just pinged them. > > Bleachbit has a fairly high popcon and is active upstream. Bleachbit's removal > would be a real loss for many users.
bleachbit port to python3 is completed and has been released as version 3.9.0 (even though is marked as a beta). Could you please prepare this new version and upload it to unstable asap? bleachbit is about to be the only rdep of python-requests in testing, so the sooner bleachbit is updated in sid, the sooner we can remove python-requests, helping with the py2removal effort. If you prefer, i can have a look at updating the package. Regards, Sandro
