On Wed, 2021-03-03 at 23:00 +0000, Sam James wrote: > > On 2 Mar 2021, at 15:05, Michał Górny <mgo...@gentoo.org> wrote: > > > > Hi, > > > > I think I've made a mistake by stabilizing PyPy(3), and I would like > > to > > drop it back to ~arch (and stable-mask the relevant flags). > > > > Roughly, there are 4 problems with it: > > > > [snip] > > > Honestly, I've tried to improve PyPy in the past but I don't really > > have > > time or motivation to do this continuously. PyPy is an interesting > > project, and it has its isolated uses. However, I don't think it's > > ready as a general-purpose Python interpreter for production > > environments. > > > > I don't really want to remove it entirely or revert all the work > > we've > > put into testing packages with it -- but I think we should move it > > to > > ~arch at the very least. > > It’s unfortunate but no objections. News item may be worthwhile > to explain to users why & how for posterity, but not necessary.
Yeah, I'm still not sure what to do. What is certain is that we need to do something because current PyPy versions are vulnerable, and two-slots-in-one-target approach is not sustainable. Option 1. is to stabilize the new versions, including alpha pypy3.7 (test-restricted). This will make it possible to delay the final decision. However, it would imply that stable users rebuild everything to upgrade pypy3 and that would suck if it would mean it goes ~arch anyway. Option 2. is to drop it to ~arch. This feels better given its quality but kinda sucks for users. When we remove py3.7, having pypy3.7 as the newest pypy will be the same kind of problem whether it's stable or not. -- Best regards, Michał Górny
