On 4/15/19 1:39 PM, Matěj Cepl wrote:

this is just your periodic remainder (which could be expected for the last 10+ years or so, so there shouldn't be any surprise) that on the bright fresh chilly morning of 2020-01-02 we are going to remove python2 package (that's Python 2.7.* interpreter) from Factory.

I really wonder why this is necessary. Given the fact that there are enterprise distros maintaining Python 2 for a much longer time there will be backport patches available for upcoming security issues. And I'm willing to take care of that. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 4/15/19 1:39 PM, Matěj Cepl wrote:

You should really really make sure to check all your tools have been already ported and tested on Python 3 right NOW.

Hopefully node-gyp will be finally be ported to Python 3 as otherwise no NodeJS in Factory because of this. The problem has to do with chromium/v8/node build system that affects sections of the npm ecosystem - who wants to touch that can of worms? https://github.com/nodejs/node-gyp/issues/1337 the issue has been going since at least 2013, https://github.com/nodejs/node-gyp/issues/193 If there is a lesson here - "don't invent your own build system!" - Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 4/15/19 2:05 PM, Matěj Cepl wrote:

Michael Ströder píše v Po 15. 04. 2019 v 13:56 +0200:

...

I really wonder why this is necessary. Given the fact that there are enterprise distros maintaining Python 2 for a much longer time there will be backport patches available for upcoming security issues. And I'm willing to take care of that.

You are free to keep your own project on OBS with packages you want to support (or use Leap), but Factory is for “the newest stable software” and “bleeding edge software”, not the museum of computer archeology.

So this is simply your personal ego-trip not to care about what others need. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 4/15/19 2:18 PM, Richard Brown wrote:

On Mon, 15 Apr 2019 at 14:13, Michael Ströder wrote:

...

On 4/15/19 2:05 PM, Matěj Cepl wrote:

...

Michael Ströder píše v Po 15. 04. 2019 v 13:56 +0200:

...

I really wonder why this is necessary. Given the fact that there are enterprise distros maintaining Python 2 for a much longer time there will be backport patches available for upcoming security issues. And I'm willing to take care of that.

You are free to keep your own project on OBS with packages you want to support (or use Leap), but Factory is for “the newest stable software” and “bleeding edge software”, not the museum of computer archeology.

So this is simply your personal ego-trip not to care about what others need.

Users want supported, secure, maintained software

https://pythonclock.org/

That does not include Python 2 after the day upstream formally, absolutely, and unquestionably abandon it.

As said. There are various installation for which back-port patches will be available, including SLE. While migrating to Python 3 is of course necessary I see no reason to fighting a crusade against people who still have to maintain Python 2 after that date. And as said: I'm willing to do work. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Apr 15, Michael Ströder wrote:

As said. There are various installation for which back-port patches will be available, including SLE.

SLES15 SP1 is already python3 only, all python2 code moved to a legacy module (which means limited support and a short lifecycle) which will be removed mid-term. As announced already two years ago, or even longer. Beside, how should SLE contain backports, if there isn't anything upstream anymore? You can only backport something if there is somebody active upstream. I wouldn't count on that. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 4/15/19 2:32 PM, Thorsten Kukuk wrote:

On Mon, Apr 15, Michael Ströder wrote:

...

As said. There are various installation for which back-port patches will be available, including SLE.

SLES15 SP1 is already python3 only, all python2 code moved to a legacy module (which means limited support and a short lifecycle) which will be removed mid-term. As announced already two years ago, or even longer.

So the python2 interpreter is removed too? I was under impression the interpreter remains for duration of SLE15.

Beside, how should SLE contain backports, if there isn't anything upstream anymore? You can only backport something if there is somebody active upstream.

I'm not sure. We distribute a lot of software that has no upstream anymore. For all intents and purposes, we are upstream for a lot of "enterprise" software. I'm quite certain that python2 will live on as some other name. - Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Apr 15, Adam Majer wrote:

On 4/15/19 2:32 PM, Thorsten Kukuk wrote:

...

On Mon, Apr 15, Michael Ströder wrote:

...

As said. There are various installation for which back-port patches will be available, including SLE.

SLES15 SP1 is already python3 only, all python2 code moved to a legacy module (which means limited support and a short lifecycle) which will be removed mid-term. As announced already two years ago, or even longer.

So the python2 interpreter is removed too?

Yes, that one has moved, too.

I was under impression the interpreter remains for duration of SLE15.

No, we always clearly stated, that this will not be the case. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dne pondělí 15. dubna 2019 13:39:10 CEST, Matěj Cepl napsal(a):

this is just your periodic remainder (which could be expected for the last 10+ years or so, so there shouldn't be any surprise) that on the bright fresh chilly morning of 2020-01-02 we are going to remove python2 package (that's Python 2.7.* interpreter) from Factory.

Running 'sudo zypper rm python2*' would now remove bleachbit, calibre, duplicity, grass, inkscape and osc. Trying to investigate Python 3 transition https://github.com/bleachbit/bleachbit is actively maintained and there is some Python 3 progress. At https://github.com/kovidgoyal/calibre and https://calibre-ebook.com/ download_linux I don't see anything about Python 3. Duplicity https://bugs.launchpad.net/duplicity/+bug/1440372 seems to be Python 3 ready soon. GRASS GIS https://svn.osgeo.org/grass/grass/branches/releasebranch_7_6/ REQUIREMENTS.html should be Python 3 in 7.8, so also hopefully soon. Regarding https://inkscape.org/ I didn't find anything. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/

On 4/15/19 2:34 PM, Dominique Leuenberger / DimStar wrote:

But, as a release manager I claim to have a say in this topic too: Dropping py2 is a noble goal, it is a high target. But if this means losing things like firefox, osc, "insertfavoriteapphere" - then you all can be sure that we will weigh the pros and cons of keeping/dropping py2. In plus, with a capable maintainer who is willing to further work on possibly reported CVEs: how can we claim it is not maintained?!

So, please, let's tone this thread down a notch: Maej formulated a goal to remove python2 by 2020 - and as a distribution I hope we can all see the benefit of not having to maintain something that is abandoned upstream. But just jumping off the cliff because upstream declares something unmaintained is not going to happen.

Let me describe my personal situation: 1. I'm supporting Linux distros like CentOS7 where the standard distro does not ship with Python3 yet. So there is some constraint there. 2. I do want to migrate to Python3. But when touching all the code I'd like make sure to really move to Python3 (especially with type hints). So I won't maintain modules compatible to both 2 and 3 to avoid all the ugly code mess you can find in various module packages. But with a Python maintainer moving stuff around, breaking existing config workflows I'm forced to implement many work-arounds wasting my time. I'd really prefer to spend this time on migrating the upstream code base! So Matěj's pushing towards Python3 effectively slows down Python3 progress on my side. And that's what really makes me angry. Ciao, Michael.

On 4/15/19 8:34 AM, Dominique Leuenberger / DimStar wrote:

Hello,

On Mon, 2019-04-15 at 13:39 +0200, Matěj Cepl wrote:

...

Hello,

this is just your periodic remainder (which could be expected for the last 10+ years or so, so there shouldn't be any surprise) that on the bright fresh chilly morning of 2020-01-02 we are going to remove python2 package (that's Python 2.7.* interpreter) from Factory.

I'm not sure if you cna word it this drastic - you can set it as a GOAL to remove python2 from Factory. Even a target date is a nice to have. And a lot of effort has already happened.

But, as a release manager I claim to have a say in this topic too: Dropping py2 is a noble goal, it is a high target. But if this means losing things like firefox, osc, "insertfavoriteapphere" - then you all can be sure that we will weigh the pros and cons of keeping/dropping py2. In plus, with a capable maintainer who is willing to further work on possibly reported CVEs: how can we claim it is not maintained?!

So, please, let's tone this thread down a notch: Maej formulated a goal to remove python2 by 2020

Well, from my perspective formulating a goal would be more along the lines of: "...the goal is to..." "... we would like to..." "... the plan is to... if possible..." However it was stated that "...we are going to remove python2 package ..." This is a declaration and an absolute statement as to what is going to happen. One should not really be surprised that such absolutes create waves. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Technical Team Lead Public Cloud rjschwei@suse.com IRC: robjo

On Mon, Apr 15, 2019 at 9:25 AM Michael Ströder wrote:

On 4/15/19 2:34 PM, Dominique Leuenberger / DimStar wrote:

...

But, as a release manager I claim to have a say in this topic too: Dropping py2 is a noble goal, it is a high target. But if this means losing things like firefox, osc, "insertfavoriteapphere" - then you all can be sure that we will weigh the pros and cons of keeping/dropping py2. In plus, with a capable maintainer who is willing to further work on possibly reported CVEs: how can we claim it is not maintained?!

So, please, let's tone this thread down a notch: Maej formulated a goal to remove python2 by 2020 - and as a distribution I hope we can all see the benefit of not having to maintain something that is abandoned upstream. But just jumping off the cliff because upstream declares something unmaintained is not going to happen.

Let me describe my personal situation:

1. I'm supporting Linux distros like CentOS7 where the standard distro does not ship with Python3 yet. So there is some constraint there.

Python 3.6 is coming to the base EL7 distribution with the 7.7 release: https://bugzilla.redhat.com/show_bug.cgi?id=1639030 Prior to this, Python 3 has been available through Software Collections in both EL6 and EL7. Python 3 is also available in EPEL for EL6 and EL7. So I don't consider this as a valid excuse, as there are ways to have a usable Python 3 environment.

2. I do want to migrate to Python3. But when touching all the code I'd like make sure to really move to Python3 (especially with type hints). So I won't maintain modules compatible to both 2 and 3 to avoid all the ugly code mess you can find in various module packages.

But with a Python maintainer moving stuff around, breaking existing config workflows I'm forced to implement many work-arounds wasting my time. I'd really prefer to spend this time on migrating the upstream code base!

Use a Tumbleweed snapshot for that. It's an effective strategy if you consider Factory churn to hurt your development process. But frankly, when I worked on getting Pagure to Python 3, I worked from Tumbleweed almost exclusively. It worked out well, even with the churn, because I could keep validating against new stuff. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 4/15/19 9:28 AM, Richard Brown wrote:

On Mon, 15 Apr 2019 at 15:20, Robert Schweikert wrote:

...

...

No, we always clearly stated, that this will not be the case.

Well SLE15 is not the only game in town, we should not forget that. SLE12 has Python 2.7 and has a lifecycle until Oct 31st 2027, add 3 years of LTSS and Python 2.7 will exist in SLE 12 10 years past the upstream EOL.

Unless of course SLE decides to break pretty much every rule we have and ditch Python 2.7.

Not that I am advocating to keep Python 2.7 in Factory until EOL of SLE 12. However the argument about "it goes away upstream" is not very strong IMHO.

But considering that, unlike SLE 15, SLE 12 and Tumbleweed have had no practical, theoretical, or even tangential codebase relationship for years now, and Leap's last SLE 12-based release reaches end of life in June this year, I don't see how your point really bring anything to the table.

Well you stated that: "Users want supported, secure, maintained software" In a context where Michael offered to do the necessary maintenance work for Python 2. Maybe you are implying that Michael is not capable of delivering according to your definition? Further, based on your statement one could easily draw the conclusion that you are either deliberately, inadvertently, or uncaringly implying that SLE will be shipping unsupported insecure software. This ML does not exist in a vacuum and everyone is well aware of the relationship between openSUSE and SLE. Therefore, IMHO, such statements probably have funny and strange ways of making people think things that may or may not have been intended. To this you will of course state that this is an openSUSE mailing list and what SLE does has no bearing to the discussion. I will then reply that SLE simply becomes the new upstream of Python 2.7 and that yes, what SLE does has bearing on openSUSE; and round and round we go. So lets be clear, SLE 12 will have a supported Python 2.7 version until 2030, at least as long as current guidelines and policies apply. This also implies that there will be fixes to Python 2.7 in case there are security issues. Given that we have someone volunteering to take such fixes and put them back into factory I fail to see why the institution of a grace period would be such a horrible thing as it appears it is made out to be. The next logical argument from those that can't wait will be that there has been a 10 year or so grace period already and that waiting any longer will not make a difference. Certainly that is a fair argument and one that I have made as well on occasion. For better or worse people have a funny way of deciding for themselves when the time is right, may it be finishing the osc port or the Firefox build system or "my_favorite_application". And yes it is a matter of tradeoffs, are we more interested in having only Python 3 or are we interested in having Firefox? Or maybe someone here will step up and fix up the Firefox build system, I don't know. But the primary Firefox maintainer already stated that it appears at this point unlikely that Firefox will be ready for days where Python 2.7 does not exist. Anyway the post that started all of this did not appear to consider such tradeoffs, and maybe that was done in previous posts, I do not know. The point is, collectively we find better solutions. The process to get there is made more difficult when lines are drawn in the sand.

I do not think anyone is suggesting that SUSE 'forward-port' to openSUSE any of their maintenance & fixes they will be conducting on their old SLE codebase.

Meanwhile, the developers of openSUSE need to assess what they are able and willing to maintain themselves.

So are you saying that Michael Stroeder is not considered part of this "developers of openSUSE" group? His comments were simply dismissed out of hand, that does not appear to be an assessment to me.

That determination appears to have been made, the reasoning is sound, the intent has been made public. I think energies are best spent figuring out mitigation strategies for any disruption this may cause, but at it's heart, any suggestion that Python2 has any life left in it appears to be a lost cause to me.

Well it has life left as long as it is needed by "my_favorite_application" and if Firefox no longer builds after 2020-01-02 then I guess for all those that consider Firefox as "my_favorite_application" it's lights out. That is certainly a path that can be chosen. Whether that is a good decision or not is up to others to decide. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Technical Team Lead Public Cloud rjschwei@suse.com IRC: robjo

понеділок, 15 квітня 2019 р. 16:01:09 EEST Vojtěch Zeisek написано:

At https://github.com/kovidgoyal/calibre and https://calibre-ebook.com/ download_linux I don't see anything about Python 3. https://github.com/kovidgoyal/calibre/commits/master A lot of py3 commits.

-- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

Am Montag, 15. April 2019, 13:39:10 CEST schrieb Matej Cepl:

Hello,

this is just your periodic remainder (which could be expected for the last 10+ years or so, so there shouldn't be any surprise) that on the bright fresh chilly morning of 2020-01-02 we are going to remove python2 package (that's Python 2.7.* interpreter) from Factory.

You should really really make sure to check all your tools have been already ported and tested on Python 3 right NOW.

Last time, I looked, the whole Openstack eco system was primary based on Py2. Not that this is relevant for Factory that much, but highly relevant to the SUSE cloud strategy, if I'm not mistaken... https://www.suse.com/products/suse-openstack-cloud/ Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Apr 15, 2019 at 4:50 PM Thorsten Kukuk wrote:

On Mon, Apr 15, Hans-Peter Jansen wrote:

...

Last time, I looked, the whole Openstack eco system was primary based on Py2.

Must be many years ago if I read the yearly progress reports of porting Openstack to python3 correctly.

...

Not that this is relevant for Factory that much, but highly relevant to the SUSE cloud strategy, if I'm not mistaken...

The python3 openstack wiki is nearly completly green, only a few orange and red entries.

There's some stupidity in how the SUSE OpenStack packages are done, but on the balance, they're _supposed_ to be Python 3 compatible now. I suspect SUSE will fix those in due time... -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org