The SciPy Stack should be self-contained (in my opinion) which means the numpy version will be explicitly listed as one of the extensions in the bundle so there's no need for it to form part of the toolchain. That was partially why I was looking into because the only reason Python needs the full intel toolchain (including MKL) is because of numpy, if we pull numpy into a SciPy Stack bundle then the minimum requirement for Python is a just a compiler.
How we would version the Stack itself is up to us it seems so I would suggest 2016.03 for now, which would be the latest version of each of the packages as of this month. On 18 March 2016 at 14:42, <[email protected]<mailto:[email protected]>> wrote: Thanks, Alan, I'll look into this following your numba example. I'm just wondering, shouldn't for example the numpy version be part of the toolchain definition? Libraries like pandas and scipy use the numpy C stuff, if I remember correctly, so that a pandas build with numpy 1.9 is different from a pandas build with numpy 1.10. Not sure if numba from your example should also suffer from this or not. Cheers, Andreas. Alan O'Cais writes: > Dear Andreas, > > I was actually going to look into this soon. What you are describing (I > think) is a Python package bundle for the SciPy > Stack<http://www.scipy.org/stackspec.html>. An example of what that might > look like is > https://github.com/hpcugent/easybuild-easyconfigs/blob/develop/easybuild/easyconfigs/n/numba/numba-0.22.1-intel-2015b-Python-2.7.11.eb > The Python dependency is given by the version suffix and the blas dependency > is provided by the toolchain itself (a toolchain is > compiler+mpi+blas/lapack/fftw) > > You could work on this yourself based on that example and I'd be happy to > help if you run into issues. > > Alan > > On 18 March 2016 at 14:20, > <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> > wrote: > I recently stumbled across easybuild, it's an amazing piece of > software -- thanks for making this available! > > I'm wondering if there is any documentation / hints available for > managing different version of the Python scientific toolstack with > easybuild. I'm thinking of toolchains like > "py27-np19-sp016-pd017-openblas" -- you get my point. So basically I'm > looking at using easybuild as a replacement for virtualenvs / Anaconda > envs. > > Is there anything I need to consider for this use case? > > Cheers, > Andreas. > > -- > Dr. Andreas Hilboll > > Center for Marine Environmental Sciences (MARUM) > - AND - > Institute of Environmental Physics (IUP) > > University of Bremen > > U3145 > Otto-Hahn-Allee 1 > D-28359 Bremen > Germany > > +49(0)421 218 > 62133<tel:%2B49%280%29421%20218%2062133><tel:%2B49%280%29421%20218%2062133> > (phone) > +49(0)421 218 98 > 62133<tel:%2B49%280%29421%20218%2098%2062133><tel:%2B49%280%29421%20218%2098%2062133> > (fax) > http://www.iup.uni-bremen.de/~hilboll -- Dr. Andreas Hilboll Center for Marine Environmental Sciences (MARUM) - AND - Institute of Environmental Physics (IUP) University of Bremen U3145 Otto-Hahn-Allee 1 D-28359 Bremen Germany +49(0)421 218 62133<tel:%2B49%280%29421%20218%2062133> (phone) +49(0)421 218 98 62133<tel:%2B49%280%29421%20218%2098%2062133> (fax) http://www.iup.uni-bremen.de/~hilboll -- Dr. Alan O'Cais Application Support Juelich Supercomputing Centre Forschungszentrum Juelich GmbH 52425 Juelich, Germany Phone: +49 2461 61 5213 Fax: +49 2461 61 6656 E-mail: [email protected]<mailto:[email protected]> WWW: http://www.fz-juelich.de/ias/jsc/EN ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
