On 7/21/19 11:47 AM, Antonio Valentino wrote: > Il 21/07/19 07:34, Sebastiaan Couwenberg ha scritto: >> On 7/7/19 7:43 AM, Sebastiaan Couwenberg wrote: >>> Besides the usual new upstream releases, we need to work on removing >>> Python 2 support for all our packages during the bullseye development >>> cycle. As mention in the release-notes [1] python2.7 is expected to be >>> removed in bullseye as it's EOL upstream by the end of the year. >>> >>> For packages that are currently python2-only, those will need to be >>> switched to python3 and uploaded to experimental to pass NEW (this >>> requires a non-source-only upload), once the package is accepted a >>> source-only upload to unstable can follow when all reverse dependencies >>> are ready (or have bugs filed against them). >> >> Can you start working on this for your packages? > > sure, I will start working on packages asap.
The biggest blockers are mipp & python-mpop which are python2-only currently. I've pushed a change to use python3 for mipp, but that's incomplete. A bunch of test fail due to UTF8 being the default in Python 3. That's not really something I want dive into further. How important are these two packages? Removing them from testing may be an option to unblock their dependencies. They keep python-pyresample in the archive for example, which in turn requires python-pyproj, and its upstream is going to drop Python 2 support. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
