[opensuse-factory] Python2 removal now in Tumbleweed
Hi all, The removal of python2-* subpackages in staging is done and now it is included in TW. Now this of course still broke some packages [1] but overall it is going smoothly (less than 10% of py packages are now unresolvable or failed). If you are maintainer of stuff thats suddenly not building you have couple of scenarios: 1) optional python2 dependency a) if you wanna backport the package to Leap15 then you can use %bcond_without python2 to condition the parts. b) or just remove all the python2 deps and code and make the package TW only if you desire so. 2) hard python2 dependency Tough luck, unless upstream switched to python3 the package will probably depart from the Tumbleweed. We will be fixing the unresolvables for the important stuff and what we directly control but for the leaf packages we will leave it up to you. Feel free to poke on #opensuse-python and ask if you are not sure on how something should be done. Cheers Tom [1] https://trello.com/c/Q84Ucri1/62-fix-python-stuff-on-tw <https://trello.com/c/Q84Ucri1/62-fix-python-stuff-on-tw> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
What will be the situation in Leap 15.2? On Mon, Apr 20, 2020 at 8:49 AM Tomáš Chvátal <tchvatal@suse.com> wrote:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Now this of course still broke some packages [1] but overall it is going smoothly (less than 10% of py packages are now unresolvable or failed).
If you are maintainer of stuff thats suddenly not building you have couple of scenarios:
1) optional python2 dependency a) if you wanna backport the package to Leap15 then you can use %bcond_without python2 to condition the parts.
b) or just remove all the python2 deps and code and make the package TW only if you desire so.
2) hard python2 dependency
Tough luck, unless upstream switched to python3 the package will probably depart from the Tumbleweed.
We will be fixing the unresolvables for the important stuff and what we directly control but for the leaf packages we will leave it up to you. Feel free to poke on #opensuse-python and ask if you are not sure on how something should be done.
Cheers
Tom
[1] https://trello.com/c/Q84Ucri1/62-fix-python-stuff-on-tw <https://trello.com/c/Q84Ucri1/62-fix-python-stuff-on-tw>
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne 20.04.2020 v 8:55 Roger Oberholtzer napsal(a):
What will be the situation in Leap 15.2?
The python2 will still be provided there. We spent quite bit of our time with Max getting the python stack sorted updated and cleaned for 15.2 so even latest modules could be used there. We will have to do a rething for this for 15.3 tho. SUSE will be providing support for the interpreter, but more and more modules are just python3 based. HTH Tom -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
2) hard python2 dependency
Tough luck, unless upstream switched to python3 the package will probably depart from the Tumbleweed.
mysql-workbench still needs a python 2 and there is no ETA for python 3 [1], so it would be removed, right? I could try to drop python at all, to have at least main functionality, anyway mysql-workbench python now is broken due to [2]. But I don't think I'll do it in several hours. So what is time window for this removing? [1] https://forums.mysql.com/read.php?152,685111,685139#msg-685139 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1169213 -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
Dne 20.04.2020 v 12:32 Mykola Krachkovsky napsal(a):
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW. Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
Python interpreter setuptools and pip will stay around for a while still. We will be slowly phasing out stuff that really just pulls the py2 for some bindings that are dead/deprecated.
2) hard python2 dependency
Tough luck, unless upstream switched to python3 the package will probably depart from the Tumbleweed. mysql-workbench still needs a python 2 and there is no ETA for python 3 [1], so it would be removed, right? I could try to drop python at all, to have at least main functionality, anyway mysql-workbench python now is broken due to [2]. But I don't think I'll do it in several hours. So what is time window for this removing?
Well the package will be unresolvable. But it won't block TW releases so I would say 'near future' (weeks). HTH Tom
понеділок, 20 квітня 2020 р. 13:39:59 EEST Tomáš Chvátal написано:
Python interpreter setuptools and pip will stay around for a while still.
We will be slowly phasing out stuff that really just pulls the py2 for some bindings that are dead/deprecated.
Got it.
Well the package will be unresolvable. But it won't block TW releases so I would say 'near future' (weeks).
HTH
Tom
Thank you. This seems fine. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3... I'm pretty Firefox is in a similar boat with Mach and mozbuild... -- 真実はいつも一つ！/ 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
Am 20.04.20 um 12:42 schrieb Neal Gompa:
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3...
I'm pretty Firefox is in a similar boat with Mach and mozbuild...
Building Firefox with just python3 still does not work for an unknown period of time. I already mentioned that a few times. It's also a totally non-trivial thing to do and I'm certainly not wasting a single minute of my lifetime on helping out with that task. I cannot remember where but somewhere I told people the upstream bugzilla tracking id so they can simply implement the switch to python 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1388447 Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 20 Apr 2020, Wolfgang Rosenauer wrote:
Am 20.04.20 um 12:42 schrieb Neal Gompa:
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3...
I'm pretty Firefox is in a similar boat with Mach and mozbuild...
Building Firefox with just python3 still does not work for an unknown period of time. I already mentioned that a few times. It's also a totally non-trivial thing to do and I'm certainly not wasting a single minute of my lifetime on helping out with that task.
I cannot remember where but somewhere I told people the upstream bugzilla tracking id so they can simply implement the switch to python 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1388447
Just embed python2 into firefox ... the question is then how much of python2 you really need. Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)
On Mon, Apr 20, 2020 at 9:08 AM Richard Biener <rguenther@suse.de> wrote:
On Mon, 20 Apr 2020, Wolfgang Rosenauer wrote:
Am 20.04.20 um 12:42 schrieb Neal Gompa:
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3...
I'm pretty Firefox is in a similar boat with Mach and mozbuild...
Building Firefox with just python3 still does not work for an unknown period of time. I already mentioned that a few times. It's also a totally non-trivial thing to do and I'm certainly not wasting a single minute of my lifetime on helping out with that task.
I cannot remember where but somewhere I told people the upstream bugzilla tracking id so they can simply implement the switch to python 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1388447
Just embed python2 into firefox ... the question is then how much of python2 you really need.
Or, you know, help Firefox upstream migrate the remainder of their Python 2 code to Python 3? They have a tracker bug (as Wolfgang linked to earlier) and there aren't that many tickets left... The SUSE Firefox maintainer would hopefully be actively engaged in this process, given that SUSE is pulling the plug on Python 2 in Tumbleweed. :) -- 真実はいつも一つ！/ 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 Mon, 2020-04-20 at 15:08 +0200, Richard Biener wrote:
I cannot remember where but somewhere I told people the upstream
bugzilla tracking id so they can simply implement the switch to python 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1388447
Just embed python2 into firefox ... the question is then how much of python2 you really need.
Worst adivse ever - why would you even suggest that :(
On Mon, 2020-04-20 at 13:45 +0200, Wolfgang Rosenauer wrote:
I'm pretty Firefox is in a similar boat with Mach and mozbuild...
Building Firefox with just python3 still does not work for an unknown period of time. I already mentioned that a few times. It's also a totally non-trivial thing to do and I'm certainly not wasting a single minute of my lifetime on helping out with that task.
You did - and it is considered; heck, Firefox and Chromium are both ring1 packages; The Staging process is rather clear: a Staging project is only mergable if all packages in the ring are building and pass the Staging QA tests - That includes Firefox for Build/QA and Chromium for build. Cheers, Dominique
On Mon, 2020-04-20 at 06:42 -0400, Neal Gompa wrote:
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3...
It means nothing like that - either you know what you claim, or please add a disclaimer to your mails that this is all speculation and you don't know more than the person asking the question. As I wrote in the last weekly review: * Removal of Python2 (VERY SOON!). We will remove all python2-FOO modules, but keep the python2 interpreter, python2-setuptools and python2-pip around. So people who need to can still base their work on that. This is supposedly happening in Week 17 Cheers, Dominique
On Mon, Apr 20, 2020 at 9:27 AM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Mon, 2020-04-20 at 06:42 -0400, Neal Gompa wrote:
On Mon, Apr 20, 2020 at 6:33 AM Mykola Krachkovsky <w01dnick@gmail.com> wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
It also means Chromium goes away too, since Google hasn't deigned to fix GN to work with Python 3...
It means nothing like that - either you know what you claim, or please add a disclaimer to your mails that this is all speculation and you don't know more than the person asking the question.
It *does* mean that. I know it's not speculation because I've been going through this process in Fedora as part of removing the Python 2 stack. We currently have exceptions in place for a small number of Python 2 modules so that all the Chromium functionality works (in particular, chrome-remote-desktop depends on python2-psutil). If I was being speculative, I would say so. Stop assuming I don't know what I'm talking about. -- 真実はいつも一つ！/ 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 Mon, 2020-04-20 at 09:32 -0400, Neal Gompa wrote:
It means nothing like that - either you know what you claim, or please
add a disclaimer to your mails that this is all speculation and you don't know more than the person asking the question.
It *does* mean that. I know it's not speculation because I've been going through this process in Fedora as part of removing the Python 2 stack. We currently have exceptions in place for a small number of Python 2 modules so that all the Chromium functionality works (in particular, chrome-remote-desktop depends on python2-psutil).
And this here is openSUSE - Fedora is no reference. If I stay Firefox can use Python2 to build, it can use python2 to build and won't have to disappear. That's my right as Release Manager - and together with the python maintainers this is the decided course. Cheers, Dominique
On Mon, Apr 20, 2020 at 9:36 AM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Mon, 2020-04-20 at 09:32 -0400, Neal Gompa wrote:
It means nothing like that - either you know what you claim, or please
add a disclaimer to your mails that this is all speculation and you don't know more than the person asking the question.
It *does* mean that. I know it's not speculation because I've been going through this process in Fedora as part of removing the Python 2 stack. We currently have exceptions in place for a small number of Python 2 modules so that all the Chromium functionality works (in particular, chrome-remote-desktop depends on python2-psutil).
And this here is openSUSE - Fedora is no reference.
I'm going to pass by this deliberately antagonistic and outright ludicrous statement.
If I stay Firefox can use Python2 to build, it can use python2 to build and won't have to disappear. That's my right as Release Manager - and together with the python maintainers this is the decided course.
And you should *read* emails better. I was indicating that it would be a problem if the interpreter was removed. That was *before* Tomas replied stating the interpreter is sticking around for a while. And *you* did accept removal of all Python 2 modules, so packages that explicitly depended on some at runtime (if they were ever explicitly declared), will break. That's fine and good if you want that. Fortunately, Chromium on openSUSE does not provide remote desktop support, so that dependency isn't a problem. I'm primarily concerned about explicit requirements of Python 2 modules. And if maintainers take attitudes like Wolfgang's, then things will just continue to break and get removed. Hopefully it won't lead to an implosion somewhere... -- 真実はいつも一つ！/ 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 Mon, 2020-04-20 at 13:32 +0300, Mykola Krachkovsky wrote:
Hi,
понеділок, 20 квітня 2020 р. 09:47:55 EEST Tomáš Chvátal написано:
Hi all,
The removal of python2-* subpackages in staging is done and now it is included in TW.
Would python-base, python-devel, etc be removed as well? Right now, removing python-base triggers removing a lot of latex packages and npm12.
As I wrote in the last weekly review: * Removal of Python2 (VERY SOON!). We will remove all python2-FOO modules, but keep the python2 interpreter, python2-setuptools and python2-pip around. So people who need to can still base their work on that. This is supposedly happening in Week 17 Packages like Firefox that still need python2 to build, can do so. But should aim (together with the respective upstreams) to eliminate that requirement. Cheers, Dominique
Hi all, To follow up a bit atm we reduced the state of TW to 2 parts: 93 unresolvable packages 155 failed packages Of course not all failures are caused by the py2 drop but in general if you look on [1] and [2] it is quite obvious that simply packages just expect to call python and kinda hoped it will be the right interpreter. At least for python modules the fix is quite straight forward [3][4]. We also plan to add back /usr/bin/python and ensure easy migration [5] but that will still take time to implement and test the update scenarios. Thanks a lot to all that fixed some packages from the stack so far :) Cheers Tom [1] https://build.opensuse.org/package/live_build_log/openSUSE:Factory/cram/stan... [2] https://build.opensuse.org/package/live_build_log/openSUSE:Factory/python-Fa... [3] https://github.com/tomerfiliba/plumbum/pull/509 [4] https://github.com/spyder-ide/qtawesome/pull/143 [5] https://trello.com/c/pPvuz7Kt/59-implement-update-alternatives-for-usr-bin-p... N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
participants (8)
-
Dominique Leuenberger / DimStar -
Mykola Krachkovsky -
Neal Gompa -
Richard Biener -
Roger Oberholtzer -
Tomas Chvatal -
Tomáš Chvátal
-
Wolfgang Rosenauer