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

2016-09-29 Thread Robert McLeod
ould appreciate if someone could > elaborate on or point me to the reasoning behind that decision. > > Thank you, > Oleksandr > > > > -Original Message- > From: NumPy-Discussion [mailto:numpy-discussion-boun...@scipy.org] On > Behalf Of Julian Taylor > Se

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
--Original Message- From: NumPy-Discussion [mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Julian Taylor Sent: Thursday, September 29, 2016 8:10 AM To: numpy-discussion@scipy.org Subject: Re: [Numpy-discussion] Using library-specific headers On 09/27/2016 11:09 PM, Pavlyk, Oleksandr wrote: &

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

[Numpy-discussion] Using library-specific headers

2016-09-27 Thread Pavlyk, Oleksandr
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 was to use #if defined(SCIPY_MKL_H) #include