On 9/7/21 19:36, Ben Greiner wrote:
Am 07.09.21 um 11:11 schrieb Simon Lees:
Constant source of confusion. The python stack on Leap is basically left as is and only sees marginal updates where absolutely necessary. If you want up to date packages, use Tumbleweed. No this is even more confusing because someone has explicitly touched it to make it older then what we are shipping everywhere else.
What do you mean by "everywhere else"? Leap 15.1 and 15.2 have always shipped pip 10 and no maintenance update did change that. Didn't only Leap 15.3 start to reuse binary packages from SLE15?
While only 15.3 started using binary packages from SLE, we have used the source packages from SLE for an increasingly large number of packages since Leap was started. From 15 we have tended to take the SLE package sources by default unless there is a really good reason not to. For pip there could have been a good reason or it could have been missed somehow. SLE got an update from 10.X to 20.X during 15-SP1 with a couple of updates since one was in 15-SP2, it shouldn't be too hard to take the sources for that package and ship them as an update for Leap unless there is a really good reason not to have a newer version like it would break lots of things for lots of people, but it already seems broken. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B