Numpy pinning about pynfft-feedstock HOT 4 OPEN

I think it can be changed to use that notation, I just haven't update this recipe since that syntax became available.

The method currently in meta.yaml was the recommended way at one point. As long as the package builds against a NumPy that is not newer than the one the user has installed, it is fine (NumPy has a policy to maintain backwards ABI compatibility). I think those specific versions were the oldest with packages available for each python version/platform.

from pynfft-feedstock.

also, I should note that pyNFFT unfortunately no longer seems to be actively maintained and if I think it only works with NFFT 3.2.x.

from pynfft-feedstock.

As long as the package builds against a NumPy that is not newer than the one the user has installed, it is fine (NumPy has a policy to maintain backwards ABI compatibility). I think those specific versions were the oldest with packages available for each python version/platform.

Ah I see, makes sense. Then it's fine to build with 1.11, say, and not to require a specific Numpy version. AFAIK the current recommended way to do that is to specify numpy: 1.11 in conda_build_config.yaml and then use host: numpy {{ numpy }} and run: numpy in meta.yaml.

from pynfft-feedstock.

also, I should note that pyNFFT unfortunately no longer seems to be actively maintained and if I think it only works with NFFT 3.2.x.

Right, it hasn't been active in a while. There has been one commit to master, though, that makes pyNFFT build against 3.3 and higher. I tested updating the recipe with current Git master, and it seems to work with 3.4.1 (I haven't tested a lot of functionality).

I was considering a PR into pyNFFT to allow different dtypes, as upstream NFFT has support for single and long double since version 3.3 or so.

from pynfft-feedstock.