Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Ondrej Novy
Hi, po 11. 11. 2019 v 12:07 odesílatel Yves-Alexis Perez napsal: > generic question about the interaction between the python transition and > current situation with NEW processing. > I think it's unrelated. State of NEW processing is stable for long time. But if you need to accept NEW

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-11-11 at 12:04 +0100, Matthias Klose wrote: > > sorry if this has been discussed already somewhere else (I stopped reading > > - -devel@ a long time ago) but is there something done to improve NEW > > processing > > here? I have two

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Matthias Klose
On 11.11.19 11:43, Yves-Alexis Perez wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-11-11 at 10:33 +0100, Ondřej Nový wrote: We are going to raise the severity of the py2removal bugs to "serious" in several steps. In the first phase we are going to raise severity of the

Re: Python 2 removal in sid/bullseye: Progress and next steps

2019-11-11 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-11-11 at 10:33 +0100, Ondřej Nový wrote: > We are going to raise the severity of the py2removal bugs to "serious" > in several steps. In the > first phase we are going to raise severity of the py2removal bugs for > all leaf module

Python 2 removal in sid/bullseye: Progress and next steps

2019-11-10 Thread Ondřej Nový
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 current or future upstream version.