On 12/25/19 5:34 AM, Norbert Preining wrote: > Hi Thomas, > > On Mon, 23 Dec 2019, Thomas Goirand wrote: >> situation of Calibre? When do you think your package will be ready? As I >> understand, Calibre itself is ready, but what about the plugins? Are the > > Kovid has announced the shift to Py3 [1], and asked the Plugin authors to > update their plugins. This is under way. At the same time several fixes > for the Py3 version were found. How far the plugins are updated I cannot > evaluate easily (as I don't use all the several hundreds of them). > >> Now, we have 2 alternatives: get routes py2 support removed, and then, >> calibre py2 removal bug becomes RC, or we attempt to reintroduce a few > > When will this happen? > >> I don't think we should wait for another 6 months to act here. > > Kovid himself plans to switch upstream officially around mid next year, > which is obviously too late for you. > > When do you want to go ahead with the removal?
As much as I understand, the AUTORM process takes about 35 days since the last activity in the BTS. If you see here: https://bugs.debian.org/938407 this leads us to the end of January. Am I correct? If we get the package AUTORM before that, then I'll upload a Py2 removal quickly. > I have more or less given up on my opposition and go with the flow, so > if it is RC it is RC and I upload the Py3 version with its shortcomings. Hopefully, this sad situation will soon be addressed. If you need some help with the Py3 porting, I'd be happy to help with that. Maybe this can help: you could give a go with something like this: apt-get install sixer for i in $(find . -iname '*.py') ; do echo "===> $i" sixer all -w $i done This usually gives rather good (but often incomplete) results, if you address all of the warning it shows (which are usually not hard to fix, like print() calls for example), and if there's no too hard to address bytes vs str problems. Hoping this helps, Cheers, Thomas Goirand (zigo)
