On 10/17/19 1:26 AM, Norbert Preining wrote: > Hi Thomas, > >> Closer to the release means that all the reverse dependencies of your >> package will have to get somehow fixed. If everyone does like this, then >> that's too much work. If possible, it'd be best if that could happen > > I agree, but let us look at reality: > - bullseye will be released maybe around spring 2021 > - Py2 will be deprecated 2020/1/1 > > I think the deprecations of Py2 will trigger a considerable shift, even > within Calibre (but I must admit, this is a guess!). That means, even if > we wait 3 months till 2020/3, there is still approximately one year to > clean up the rest. The last *2* month have seen a considerable shift to > Py3 in Debian, so I guess that a year will be sufficient (ok, deducing > freeze period etc say 6 months). > > So yes to your argument - I will not wait till shortly before the > release of Bullseye, but I will wait to see what happens after 2020/1/1 > in Calibre. > > Best > > Norbert
Hi Norbert, Waiting 3 to 6 months in this case seem very sensible to me. Thanks for reconsidering as you did. Cheers, Thomas Goirand (zigo)
