On Fri, Aug 30, 2019 at 07:33:16AM +0000, Matthias Klose wrote: > Package: src:pycryptopp > Version: 0.7.1-4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > 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.
Hi Vasudev, https://github.com/tahoe-lafs/pycryptopp/issues/36#issuecomment-504130020 states: | The Tahoe-LAFS project has decided it is not interested in porting | pycryptopp to Python 3. Instead, Tahoe-LAFS is switching to the | "cryptography" library. | | I don't have any problem with anyone else taking on this porting effort | but I'm closing this to reflect the fact that the maintainers have | no plans of taking this on. Given that the now removed tahoe-lafs was the only reverse dependency, let's also remove pycryptopp? Cheers, Moritz
