Comment # 3 on bug 1177260 from Stefan Br�ns

I have no problem with using plain BLAS on architectures where openBLAS does
not exist (e.g. RISC-V, its vectorization support does not fit openBLAS) or
which are so rarely used the extra (theoretical) support burden does not pay
off.

The current change, regardless of the performance, causes fragmentation and
extra work:

- The HPC builds do not run the test suite, regressions can go in unnoticed
- when openBLAS is good enough for HPC, it should be good enough for regular
use
- Having different code for e.g. Leap/SLE and Tumbleweed doubles the work
required when there are bugs specific to either BLAS or openBLAS.

numpy is used as the canonical array format for python bindings of many
scientific packages, many of these are not available as HPC modules (and as far
as I can see, HPC modules do not exist for Leap). IMHO with this change Leap
becomes an unusable toy not meant for scientific work.