On Thu, 5 Dec 2019 at 21:33, Giovanni Mascellani <g...@debian.org> wrote: > > Il 05/12/19 22:15, Dimitri John Ledkov ha scritto:>> Also, I hope to > finish working on 1.71 as soon as possible, so that we > >> can start that migration. > > > > But 1.71 for sure will not have python2 bindings enabled. Thus > > re-enabling python2 in boost is a stopgap until December 18th when > > those reverse-deps will be removed from testing anyway. > > Wait, where does this date (December 18th) come from? Will all Python 2 > packages get deleted on that date? Is this documented anywhere? > > If it is already decided that Python 2 is going away very soon anyway (I > didn't know this and I cannot find it written anywhere), then I agree > there is no reason to re-enable Python 2.
All python2 bugs for leaf packages have been made RC on like 30th of november, causing a tonne of packages to be scheduled for autoremoval. Most of them are on 18th/19th December. See tracker.d.o for various leaf packages. And mirage itself, has already been removed from testing, has no reverse deps, and is ready to be removed from unstable too. Not quite sure why it hasn't already been removed from unstable. -- Regards, Dimitri.
