choice of a name for an openblas wheel

[carlkl]

I intend to deploy OpenBLAS as a wheel, that installs all files into the mingwpy folder. For the windows/mingwpy case mingwpy is located in <pythonroot\share\mingwpy>, hence OpenBLAS as well as other libraries would be placed into <pythonroot\share\mingwpy\opt>.

I want to recall @njs suggestion to name wheels with library development files clib_<libraryname>##.whl, i.e. clib_openblas-0.1.15-cp34-none-win_amd64.whl. Is this the right approach?

[matthew-brett]

Sounds reasonable to me.

[ogrisel]

+1 as well.

[carlkl]

As a remark to the hangout yesterday:

A somewhat rushed written RFC: let the BLAS/Lapack be interchangable by the user

I near future the idea to use a generic name for a DLL containing BLAS/Lapack routines could be tested, i.e. name it clib_blaslapack.dll. This DLL should export all standard BLAS and Lapack routines.

To would allow the user to change the underlying BLAS/Lapack machinery according to its needs.

To make a change of the implemenation happen a DLL provided by an extra package has to be loaded into the process space beforehand import of numpy. This DLL could be loaded into the process space with the help of ctypes. The selection of the desired implementation could be done with the setting of a environment variable or with a small helper function.

numpy itself could be deployed with a default implementation, say ATLAS, so changing this is optional and should be controlled by the user.