On 05 mai 2020 20:50, Florian Höch wrote:
> Hey, just letting you know upstream is indeed still alive.
>
> As you have noticed, things take longer than expected, and not all is
> due to the move to Python3. While I appreciate the offer to help, at
> the moment it would make things harder to juggl
On 05 mai 2020 20:50, Florian Höch wrote:
> Hey, just letting you know upstream is indeed still alive.
>
> As you have noticed, things take longer than expected, and not all is
> due to the move to Python3. While I appreciate the offer to help, at
> the moment it would make things harder to juggl
Hey, just letting you know upstream is indeed still alive.
As you have noticed, things take longer than expected, and not all is
due to the move to Python3. While I appreciate the offer to help, at the
moment it would make things harder to juggle for me.
The reason there is no commits over at
On Wed, 22 Apr 2020, Christian Marillat wrote:
On 17 avril 2020 11:32, Scott Talbert wrote:
[...]
It looks like upstream doesn't seem to be making much progress on
this. Do you think that we need to start working on Python 3 support
ourselves?
Duplicate work is a bad idea.
Otherwise upst
On 17 avril 2020 11:32, Scott Talbert wrote:
[...]
> It looks like upstream doesn't seem to be making much progress on
> this. Do you think that we need to start working on Python 3 support
> ourselves?
Duplicate work is a bad idea.
Otherwise upstream is still active in displaycal forums (18/
On Wed, 23 Oct 2019 07:58:05 +0200 Christian Marillat
wrote:
> On 23 oct. 2019 02:33, mo...@debian.org wrote:
>
> > Source: displaycal
> > Version: 3.8.7.1-3
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> >
> > Python2 becomes end-
6 matches
Mail list logo
