On Fri, Mar 31, 2017 at 6:30 PM, Nick Coghlan <[email protected]> wrote: > On Sun, Mar 26, 2017 at 12:50 AM, meson <[email protected]> wrote: >> Hi, >> >> is there any estimate on when Python 3.6 will be available as SCL? >> >> Our devs are asking about it. If it's going to take a long time, I'll try my >> hand at building the packages myself. > > It likely makes sense to have some community maintained sclo-* Python > packages
I've been mulling this idea over for the past couple of weeks, and I'm wondering if it might make sense to create a rolling "sclo-python3" SCL, that's initially forked from https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but explicitly promises to rebase to new Python feature releases when they come out. So if people were happy to always run on the leading edge (even for X.Y.0 releases), they could use "sclo-python3", but if they wanted to stay on a particular X.Y release for a while, they would need to switch to the downstream rh-pythonXY SCLs. Remi, if I wanted to do that, where would I start? https://github.com/sclorg-distgit is useful as a reference for submitting changes to existing community SCLs, but it doesn't provide any guidance on how to start a new one (and that info is also missing from the wiki). Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane _______________________________________________ SCLorg mailing list [email protected] https://www.redhat.com/mailman/listinfo/sclorg
