#17 Switch System Python3 to a supported version
Opened 2 years ago by lkocman. Modified 4 months ago

Already mentioned the Python version (3.6) is quite old. I wanted to test the RC version but one of my software needed Python>=3.8, so I looked at the https://software.opensuse.org/package/python38, but that package was not build for the upcoming 15.3 (only for 15.1, 15.2 and Tumbleweed, see https://build.opensuse.org/package/show/devel%3Alanguages%3Apython%3AFactory/python38). Maybe it would be a good idea to compile the official/experimental "extra" repos also against the upcoming release (after the first ISO-realese in the Beta- or RC-Phase), if there is enough manpower and compute power (free at the OBS builders). The package python38 is still not "officially" build for 15.3 two weeks after the release.

Metadata Update from @lkocman:
- Issue tagged with: SLE-Rejected

2 years ago

This is the major blocker for python refresh in Leap 15.3 majority of failed packages are python related https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP4:SLECandidates

We did receive a confirmation from maintainer that plan for the default python is to remain at 3.6. We offer "limited" availability of python39 stack and that's the situation we'd like to keep in code stream 15.

This is currently in weird state as the OPENSUSE jira is linked to parallel support of 3.8/3.9 in SLE. https://jira.suse.com/browse/PM-1482 which is already implemented.

Metadata Update from @Pharaoh_Atem:
- Custom field SUSE Jira adjusted to https://jira.suse.com/browse/OPENSUSE-41

2 years ago

Is there a way we can refine this ticket to something acceptable, or should we close this with the Rejected status?

Lubos to talk to Max Lin, about update on python38 related build failures in https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP4:SLECandidates I see significantly less build failures (something like two pages, compared to hundreds before).

As per agreement we're aiming with feature for SLE 15 SP6. As of now it's not certain if this release will happen. It's also possible that by that time SLE 15 could have a successor that we'll base the next Leap up on.

So as of now it's relatively unlikely that Leap 15 users will get python 3.8 as default.

Missing milestone 15.6

Moving to new 15.6 milestone and setting back to pending acceptance.

Metadata Update from @Pharaoh_Atem:
- Issue untagged with: SLE-Rejected
- Issue set to the milestone: 15.6 (was: 15.4)
- Issue tagged with: SLE-Accept-Pending

2 years ago

Actually, since we don't know if 15.6 is a thing, I'm moving it to Next.

Metadata Update from @Pharaoh_Atem:
- Issue set to the milestone: Next (was: 15.6)

2 years ago

15.6? Are you kidding?
Just noticed some python packages start dropping support for python 3.6 - I feel an upgrade to 3.8 is necessary, maybe with 3.6 as update-alternative?

The Python 3.8 runtime will be introduced in SLE 15.4, but there will be no total stack rebuild for the Python 3.8 runtime (which is what this is asking for).

The Python 3.8 runtime will be introduced in SLE 15.4, but there will be no total stack rebuild for the Python 3.8 runtime (which is what this is asking for).

Why 3.8 instead of just updating 3.9 already shipping in 15.3?

Metadata Update from @Pharaoh_Atem:
- Issue set to the milestone: ALP (was: Next)

10 months ago

Todo this feature needs to be re-done for purpose of Leap 15.5 (the last Leap 15.X release). The main goal is find a way to allow maintainers to update community maintained python packages to more recent versions. I'd not go with scope of this feature any further than this. Given the fact that we'll steer development to ALP https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/SHINA373OTC7M4CVICCKXDUXN5C3MYX3/

For 15.5 we should consider Python 3.10, if possible

Metadata Update from @lkocman:
- Custom field SUSE Jira - SUSE Linux Enterprise adjusted to https://jira.suse.com/browse/PM-3390

9 months ago

I can oly second DocB's comment. 3.10 still offers exactly the middle ground, that is required here: a long enough lifetime, mature point in development, but not something like the massive 3.11 update, that comes with a significant performance boost, but also with higher risks to break depending projects.

This is not going to happen in the SLE 15 code stream, since it's a massive ABI break. Moreover, SUSE is providing maintenance of Python 3.6 for SLE 15 for its lifetime in order to satisfy their customers' needs.

That said, alternative Python versions can be made available and someone can set up a project to build all the modules for those runtimes and ship it in Backports/PackageHub.

Login to comment on this ticket.