On 03.07.2022 14:22, Jon Turney wrote:
On 29/05/2022 16:54, Jon Turney wrote:
Following is a sort of RFC, so let me know your opinion.
Currently we have two type of Python packages
1) Pure python that exists at max as 2.7 3.6 3.7 3.8 3.9 plus 2 and 3
in that case 2/2.7 3/3.6 are EOL;
On 29/05/2022 16:54, Jon Turney wrote:
Following is a sort of RFC, so let me know your opinion.
Currently we have two type of Python packages
1) Pure python that exists at max as 2.7 3.6 3.7 3.8 3.9 plus 2 and 3
in that case 2/2.7 3/3.6 are EOL;
I stopped last year to update the 2.7
On 29/06/2022 16:36, Hamish McIntyre-Bhatty wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
On 29/06/2022 16:46, Marco Atzeri wrote:
On 29.06.2022 17:36, Hamish McIntyre-Bhatty wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall
On 29.06.2022 17:36, Hamish McIntyre-Bhatty wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
distibution.
As we have a lot of python3-* is obsoleded
On 03/01/2022 21:42, Marco Atzeri wrote:
On 03.01.2022 18:37, Jon Turney wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Other point:
As 3.5 was never really deployed, I think we can remove it from the
distribution.
Agreed. I have started
On 08.01.2022 17:32, Jon Turney wrote:
Whilst testing this, I note in passing that /usr/bin/pip3.9 has a
'/usr/bin/python' shebang.
So it fails to work correctly (acting as pip3.8 ?) after
'usr/sbin/alternatives --set python /usr/bin/python3.8'
thanks for the advice
upstream changed the
On 04/01/2022 16:05, Marco Atzeri wrote:
On 03.01.2022 18:37, Jon Turney wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Thanks.
Other point:
As 3.5 was never really
On 03.01.2022 18:37, Jon Turney wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Thanks.
Other point:
As 3.5 was never really deployed, I think we can remove it from the
On 03.01.2022 18:37, Jon Turney wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Other point:
As 3.5 was never really deployed, I think we can remove it from the
distribution.
As we have a lot of python3-* is obsoleted py python36-*
what is
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Thanks.
Other point:
As 3.5 was never really deployed, I think we can remove it from the
distribution.
As we have a lot of
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
distibution.
As we have a lot of python3-* is obsoleded py python36-*
what is the best way to
13 matches
Mail list logo
