LS, TW should be a rolling release and has for the most part the latest version of packages. Alas, Python is not one of them. Python now is at version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one tries to cross-compile Python-3.10.1. It is not possible to do so because Python needs - by (bad?) design - a similar version major/minor version on the building machine. So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1? Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from the same issue, is there a workaround for Python? Regards, Frans.
Op dinsdag 28 december 2021 20:31:50 CET schreef Frans de Boer:
LS,
TW should be a rolling release and has for the most part the latest version of packages. Alas, Python is not one of them. Python now is at version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one tries to cross-compile Python-3.10.1. It is not possible to do so because Python needs - by (bad?) design - a similar version major/minor version on the building machine.
So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1? Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from the same issue, is there a workaround for Python?
Regards, Frans.
Eh ... knurpht@Tuxedo-laptop:~> python3.9 --version Python 3.9.9 -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 28/12/2021 20:42, Knurpht-openSUSE wrote:
Op dinsdag 28 december 2021 20:31:50 CET schreef Frans de Boer:
LS,
TW should be a rolling release and has for the most part the latest
version of packages. Alas, Python is not one of them. Python now is at
version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one
tries to cross-compile Python-3.10.1. It is not possible to do so
because Python needs - by (bad?) design - a similar version major/minor
version on the building machine.
So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1?
Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from
the same issue, is there a workaround for Python?
Regards, Frans.
Eh ...
knurpht@Tuxedo-laptop:~> python3.9 --version Python 3.9.9
--
Gertjan Lettink a.k.a. Knurpht
openSUSE Board
openSUSE Forums Team
Yes, Python 3.9.9 is available, but you should still have 3.8.12 because of dependencies. Also, 3.9.9 is not 3.10.x, which is already around for some time. --- Frans -- A: Yes, just like that A: Ja, net zo Q: Oh, Just like reading a book backwards Q: Oh, net als een boek achterstevoren lezen A: Because it upsets the natural flow of a story A: Omdat het de natuurlijke gang uit het verhaal haalt Q: Why is top-posting annoying? Q: Waarom is Top-posting zo irritant?
Hi, Am 28.12.21 um 20:31 schrieb Frans de Boer:
LS,
TW should be a rolling release and has for the most part the latest version of packages. Alas, Python is not one of them. Python now is at version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one tries to cross-compile Python-3.10.1. It is not possible to do so because Python needs - by (bad?) design - a similar version major/minor version on the building machine.
So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1? Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from the same issue, is there a workaround for Python?
Regards, Frans.
We are in the process of activating the python310 flavor. Have a look at the staging project [1]. (Not right now, but in a few hours when the ordered-dict request is revoked or superseded, as there has been a misguided attempt to remove python36 the wrong way (*)). That said, you already have the Python 3.10 interpreter installable in Tumbleweed. Just do `zypper in python310`. All **development** of python packages should be done inside of virtual environments using this interpreter and getting everything else from PyPI. The python310 flavor is for **system packages** using python modules they depend on. The primary flavor here is still python 3.8 which is fully supported upstream and a reasonable choice for running stable software. Even without the python310 flavor globally activated, you are already able to compile against Python 3.10.1 in your own obs project. If you are familiar with the singlespec system [2], you just need to add python310 to the %pythons macro and include all modules in your dependency tree into the project. The python-rpm-macros in openSUSE:Factory are already python310 capable as of yesterday. [1] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:O [2] https://en.opensuse.org/openSUSE:Packaging_Python - Ben (*) BTW, when are we going to remove python36 from TW? Upstream EOLd it last week.
On Tue, 28 Dec 2021 20:31, Frans de Boer <frans@...> wrote:
LS,
TW should be a rolling release and has for the most part the latest version of packages. Alas, Python is not one of them. Python now is at version 3.10.1, but TW is still at 3.8.12. That is an obstacle when one tries to cross-compile Python-3.10.1. It is not possible to do so because Python needs - by (bad?) design - a similar version major/minor version on the building machine.
So, I wonder why is Opensuse TW so far behind with regard to Python-3.10.1? Also, the packages 'file' and 'Ncurses´ have workarounds - they suffer from the same issue, is there a workaround for Python?
AFAIK: the step from 3.8 to 3.10 exposes some "forced incompatibilies". See: Whats New Docs for 3.10 and 3.9 esp the "Deprecated" and "Removed" Sections, as well as the C-Api stuff further down: https://docs.python.org/3/whatsnew/3.10.html#deprecated https://docs.python.org/3/whatsnew/3.10.html#removed https://docs.python.org/3.9/whatsnew/3.9.html#deprecated https://docs.python.org/3.9/whatsnew/3.9.html#removed The impact is much bigger than the "version number" implies. cpython, libs, all the distro included python apps, etc. - Yamaban.
participants (4)
-
Ben Greiner -
Frans de Boer -
Knurpht-openSUSE -
Yamaban