Re: [Numpy-discussion] Using library-specific headers

2016-09-29 Thread Robert McLeod
Pavlyk, NumExpr optionally includes MKL's VML at compile-time. You may want to look at its implementation. From what I recall it relies on a function in a bootstrapped __config__.py to determine if MKL is present. Robert On Thu, Sep 29, 2016 at 7:27 PM, Pavlyk, Oleksandr <

Re: [Numpy-discussion] Using library-specific headers

2016-09-29 Thread Robert Kern
On Thu, Sep 29, 2016 at 6:27 PM, Pavlyk, Oleksandr < oleksandr.pav...@intel.com> wrote: > Related to numpy.random_inter, I noticed that the randomstate package, which extends numpy.random was > not being made a part of numpy, but rather published on PyPI as a stand-alone module. Does that mean

Re: [Numpy-discussion] Using library-specific headers

2016-09-29 Thread Pavlyk, Oleksandr
Hi Julian, Thank you very much for the response. It appears to work. I work on "Intel Distribution for Python" at Intel Corp. This question was motivated by work needed to prepare pull requests with our changes/optimizations to numpy source code. In particular, the numpy.random_intel

Re: [Numpy-discussion] Using library-specific headers

2016-09-29 Thread Julian Taylor
On 09/27/2016 11:09 PM, Pavlyk, Oleksandr wrote: Suppose I would like to take advantage of some functions from MKL in numpy C source code, which would require to use #include “mkl.h” Ideally this include line must not break the build of numpy when MKL is not present, so my initial approach