Re: [Numpy-discussion] Determining NPY_ABI_VERSION statically in compiled extensions

Matti, That doesn't quite cover my use case. I'm interested in querying a .whl file containing .so files that were compiled against numpy (not my currently installed version of numpy) to determine the conditions under which those `.so` files were compiled. -Robert On Mon, Oct 8, 2018 at 5:26 PM

Re: [Numpy-discussion] ndrange, like range but multidimensiontal

since ndrange is a superset of the features of ndindex, we can implement ndindex with ndrange or keep it as is. ndindex is now a glorified `nditer` object anyway. So it isn't so much of a maintenance burden. As for how ndindex is implemented, I'm a little worried about python 2 performance seeing a

Re: [Numpy-discussion] Determining NPY_ABI_VERSION statically in compiled extensions

On 08/10/18 23:31, Robert T. McGibbon wrote: Is anyone aware of any tricks that can be played with tools like `readelf`, `nm` or `dlopen` / `dlsym` in order to statically determine what version of numpy a fully-compiled C extension (for example, found inside a wheel) was compiled against? Even

[Numpy-discussion] Determining NPY_ABI_VERSION statically in compiled extensions

Is anyone aware of any tricks that can be played with tools like `readelf`, `nm` or `dlopen` / `dlsym` in order to statically determine what version of numpy a fully-compiled C extension (for example, found inside a wheel) was compiled against? Even if it only worked with relatively new versions of

Re: [Numpy-discussion] ndrange, like range but multidimensiontal

I'm open to adding ndrange, and "soft-deprecating" ndindex (i.e., discouraging its use in our docs, but not actually deprecating it). Certainly ndrange seems like a small but meaningful improvement in the interface. That said, I'm not convinced this is really worth the trouble. I think the nested

Re: [Numpy-discussion] ndrange, like range but multidimensiontal

On 10/8/18 12:21 PM, Mark Harfouche wrote: > 2. `ndindex` is an iterator itself. As proposed, `ndrange`, like > `range`, is not an iterator. Changing this behaviour would likely lead > to breaking code that uses that assumption. For example anybody using > introspection or code like: > > ``` > ind

Re: [Numpy-discussion] ndrange, like range but multidimensiontal

Allan, Sorry for the delay. I had my mailing list preferences set to digest. I changed them for now. (I hope this message continues that thread). Thank you for your feedback. You are correct in identifying that the real feature is expanding the `ndindex` API to support slicing. See comments about