Hi Norbert, cherrypy3 got python2 removed because the same happened to objgraph before that. See: https://tracker.debian.org/news/1060068/accepted-objgraph-341-2-source-into-unstable/
I don't mind reverting the change to cherrypy3, but the the work must be done on objgraph first, otherwise cherrypy3 wont build. Though I find it particularly counter-productive, since we're not seeing any progress being done on calibre, neither upstream or in Debian. There's no need to drag your feet, or complain, it wont change the fact that Python2 is being removed from Bullseye because it's dead upstream on the 1st of January next year. Making artificially cherrypy3 RC buggy, while the package is in perfect shape isn't helpful either, and this needs to be reverted. Your thoughts? Cheers, Thomas Goirand (zigo) P.S: Please don't be aggressive with me or anyone else, as you are used to, this wont help. Doing BTS ping-pong wont help either.
