Hi Mo,
On Tue, 12 Nov 2019, Mo Zhou wrote:
> How many users still use these unmaintained scripts? Could you please
> provide us a reference/estimated popcon so we can better understand the
> situation of texlive in terms of py2rm.
Popcon does not help, since these scripts are part of a huge colle
On Tue, Nov 12, 2019 at 10:07:26AM +0900, Norbert Preining wrote:
> Yes, we have a lot of python scripts, and some have been written more
> than 10 years ago, and there is no maintainer anymore.
> ...
> And *we* at the TeX side prefer not to simply throw out old stuff, see
> above.
How many users
Hi Matthias,
On Mon, 11 Nov 2019, Matthias Klose wrote:
> sure, and when everybody is doing that, we end up with Python2 in bullseye+2
> as well. Python3 is around for 10+ years now...
Well, the whole py2/py3 mess shouldn't have happened at all, but this is
not any of our faults, but purely Pytho
Hi Ondrey, hi all,
thanks to you (and all the others) for answers.
> It's team work, I "only" sent that email :). It looks like others already
Yes, in this sense with "you" I meant the Python Team and everyone
working on it.
> time line=now. 1.5 year is really short period for doing so much wor
Scott Kitterman schrieb:
> One maintainer doesn't get to block the removal of an entire stack like Qt4.
> I think there's a reasonable point of discussion about when RoQA is
> appropriate, but there comes a time when stuff just has to go.
> That doesn't make it a free for all, but for old, unsuppo
Sorry for top post, I am just on my phone. Just my two cents - the RoQA is a
pretty standard thing when you deal with bigger transitions and there’s a lot
of unmaintained packages.
Been there couple of times, and it was nowhere near py2 removal magnitude. So,
I just want to send huge thanks tow
Hi,
po 11. 11. 2019 v 16:27 odesílatel Norbert Preining
napsal:
> thanks for your work on the Python2 removal.
>
It's team work, I "only" sent that email :). It looks like others already
replied, but
Could you please give a time line of how you are planning to proceed?
>
time line=now. 1.5 ye
On November 11, 2019 3:10:32 PM UTC, Norbert Preining
wrote:
>Hi Ondřej,
>
>(please Cc, I am not subscribed to debian-devel)
>
>thanks for your work on the Python2 removal.
>
>On Mon, 11 Nov 2019, Ondřej Nový wrote:
...
>
>Furthermore,
>
>> We will also then file bug reports against ftp.debian
On 11.11.19 16:10, Norbert Preining wrote:
Hi Ondřej,
(please Cc, I am not subscribed to debian-devel)
thanks for your work on the Python2 removal.
On Mon, 11 Nov 2019, Ondřej Nový wrote:
We are going to raise the severity of the py2removal bugs to "serious"
in several steps. In the
...
Co
Hi, I'm going to answer, even if I'm not Ondrej :)
On Tue, Nov 12, 2019 at 12:10:32AM +0900, Norbert Preining wrote:
> On Mon, 11 Nov 2019, Ondřej Nový wrote:
> > We are going to raise the severity of the py2removal bugs to "serious"
> > in several steps. In the
> ...
>
> Could you please give
Hi Ondřej,
(please Cc, I am not subscribed to debian-devel)
thanks for your work on the Python2 removal.
On Mon, 11 Nov 2019, Ondřej Nový wrote:
> We are going to raise the severity of the py2removal bugs to "serious"
> in several steps. In the
...
Could you please give a time line of how you
On 11.11.19 10:33, Ondřej Nový wrote:
Hi,
We are aiming to remove Python 2 for the bullseye release, or at least
remove as many Python 2 related packages as possible. Python 2 is
discontinued upstream, but crucially, more and more providers of Python
modules don't support Python 2 in either the
12 matches
Mail list logo
