There is an inconsistency in the documentation for NPY_INOUT_ARRAY. cf. http://docs.scipy.org/doc/numpy/user/c-info.how-to-extend.html#NPY_INOUT_ARR... http://docs.scipy.org/doc/numpy/reference/c-api.array.html#NPY_INOUT_ARRAY The first link includes the flag NPY_UPDATEIFCOPY. Checking the code seems to confirm that the correct version is that in the first link, and also that NPY_OUT_ARRAY is wrong in the API docs. I haven't checked NPY_INOUT_FARRAY or NPY_OUT_FARRAY. Cheers, Henry
Does anyone care about this? Is there an alternative channel for such information, perhaps a bug report? Cheers, Henry On Fri, 2010-10-29 at 13:32 +0100, Henry Gomersall wrote:
There is an inconsistency in the documentation for NPY_INOUT_ARRAY.
cf. http://docs.scipy.org/doc/numpy/user/c-info.how-to-extend.html#NPY_INOUT_ARR... http://docs.scipy.org/doc/numpy/reference/c-api.array.html#NPY_INOUT_ARRAY
The first link includes the flag NPY_UPDATEIFCOPY. Checking the code seems to confirm that the correct version is that in the first link, and also that NPY_OUT_ARRAY is wrong in the API docs.
I haven't checked NPY_INOUT_FARRAY or NPY_OUT_FARRAY.
Cheers,
Henry
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Thu, 04 Nov 2010 12:17:01 +0000, Henry Gomersall wrote:
Does anyone care about this? Is there an alternative channel for such information, perhaps a bug report?
We care, but just posting to the ML is not the best way to get minor bugs fixed, due to the high list volume. Alternative channels: (i) Fix it yourself. http://docs.scipy.org/doc/numpy/user/c-info.how-to- extend.html#NPY_INOUT_ARRAY Check the "Edit this page" link in the left sidebar. You'll need to register an account and after that ask for activation (eg. via mailing here). (ii) Fix it yourself (b). http://docs.scipy.org/doc/numpy/dev/gitwash/patching.html (iii) File a bug ticket. -- Pauli Virtanen
participants (2)
-
Henry Gomersall -
Pauli Virtanen