Hi Am 12.05.22 um 21:05 schrieb Joe Salmeri:
Dne 08. 04. 22 v 22:56 Matěj Cepl napsal(a):
Dne 08. 04. 22 v 22:14 Dominique Leuenberger / DimStar napsal(a):
Haven't seen or heard anything from the python maintainers on that topic for a while now (also no active staging in place; presumably they are working on the devel project space first). Last I know there were some low-lever blockers. Not sure if those are fixed by now.
Matej: do you know anything specific there? Any ETA? The most problematic packages python-distributed and python-dask are in Factory, so we >> may decide on MOnday to go ahead with switching to python310. Best, Matěj The last message on the switch to python310 was back on 04/09/2022 which indicated that the switch might happen on Monday which would have been 04/11. I think that statement was merely an indication that the there would be made decision on that monday whether the SUSE python maintainers would START to tackle the switch.
It has been a month since then and I have not seen any update or mention of it.
It took a few more days, but then there was this message from DimStar last week: Am 06.05.22 um 15:11 schrieb Dominique Leuenberger / DimStar:
* Python 3.10 as default interpreter (Staging:A for the curious ones)
So, if you are interested in getting python 3.10 as the primary interpreter (I am curious, why do you need it which can't be met by the non-primary pyhton310 flavor?), feel free to submit fixes for the failing packages in [0]. Some already have a submit request pending, some are more difficult. I was working on virtualbox today, but had to stop due to other duties and might not get back at it in the next days. Pick you can pick it up at [1]. There are more python 3.10 related fixes of the xpcom18a4 library than [2].
Is there an update on the switch to python310 or an estimated ETA ?
I think it will still need a couple of days until everything is resolved. And that is only Ring1. As soon as it is in, many packages outside of it will fail. A common failure mode is that a package uses an old autoconf which cannot deal with the 4 character long min-major version string of Python 3.10. Yes, really. Can be fixed by something like [3, 4]. - Ben [0] https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:A?defaul... [1] https://build.opensuse.org/package/show/home:bnavigator:branches:Virtualizat... [2] https://www.virtualbox.org/changeset/90537/vbox [3] https://build.opensuse.org/request/show/975918 [4] https://build.opensuse.org/request/show/975799