Thomas,
On Mon, Oct 14, 2019 at 04:05:04PM +0200, Thomas Goirand wrote:
>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
Hi Thomas,
On Tue, 15 Oct 2019, Thomas Goirand wrote:
> It's been nearly a month that the calibre package is in this shape, ie
> not converted to Python 3. Besides this:
Wrong. If you could step down from your github hate line, you could
check the experimental branch of the debian calibre
Hi Norbert,
I wrote to you not to be aggressive, because I've seen so many posts of
yours toward everyone. Yet, you still call me a liar. On top of this,
you give yourself the permission to lecture me about the CoC. Well done!
Now, let be still, despite your tone, to go to the bottom of the
On Mon, 14 Oct 2019 16:05:04 +0200 Thomas Goirand wrote:
> it wont change the fact that Python2 is being removed from Bullseye
because it's dead upstream on the 1st of January next year.
That's not a fact, Bullseye can still ship with Python 2 if needed
Hi Thomas,
thanks for your email.
In case you decide to return to generally agreed upon community
standards of communication, including the CoC, and stop spreading
FUD and lies, I will happily discuss with you the issues at hand.
FUD and lie:
> particularly counter-productive, since we're not
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
6 matches
Mail list logo
