Re: Bullseye development cycle (source-only uploads & python2 removal)
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  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?
The xarray issue in pyresample (#932509) will just be the first of many.
Make sure to file bugreports for reverse dependencies (not maintained by
the team) that will need to remove their Python 2 support to unblock the
removal in your packages.
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1