> On 15 Aug 2018, at 12:18, Kenneth Hoste <[email protected]> wrote: > > Dear Joachim, > > On 15/08/2018 11:29, Joachim Hein wrote: >> Hi, >> I noticed https://github.com/easybuilders/easybuild-easyconfigs/issues/6682 >> and https://github.com/easybuilders/easybuild-easyconfigs/pull/6703 >> I am presently working on moving python packages to foss and intel 2018b >> (h5py was merged, so did boost with python). Could there please be a >> discussion/statement how we want to handle this? >> Also, we need to think how we want to share such important info in our >> community? Discussion in slack seems not to be working (the channel is to >> busy in my view). Stumbling about stuff on GitHub is in my view not the >> best way to share info like that. >> Thanks for reading. > > I was planning to also share this on the mailing list, but you beat me to it. > > The plan is outlined at > https://github.com/easybuilders/easybuild-easyconfigs/issues/6682#issuecomment-413003200, > in short: > > * get the easyconfigs for Python 3.6.6 with */2018b merged (see > https://github.com/easybuilders/easybuild-easyconfigs/pull/6703) > > * rework easyconfigs already in develop to use Python 3.6.6 rather than 3.7.0 > >
Kenneth, Thanks. Are we withdrawing 3.7 or adding 3.6.6? There is something to be said for keeping the 3.7.0 but have the 3.6.6 as the preferred and better supported option. Similar to what we have in the GCC space. We often have a conservative GCC in the standard toolchains, but offer more modern versions (e.g. GCC 8.1) as an option with limited support. The question is, how one would communicate that to users … Is it an option to have an EB quick release, that only releases the new Python 3.6.6 (and a few add ons)? Having that in a proper release makes developing python packages (like h5py) so much easier (at least for my workflow). Best wishes joachim > regards, > > Kenneth
