I think you can always using order="F" in your own code. If you patched NumPy and then the downstream libraries had to use your customized NumPy I think you would see some breaks. Probably not a lot, since many use the python numpy API which handles C or F well. Some code does do things like call array.flat after creating an array with default arguments from a list or using "copy=True" and then expects the data to be ordered as if order="C".
Kevin On Sat, Nov 11, 2023 at 3:03 PM Valerio De Benedetto <po...@debevv.com> wrote: > Hi, I found that the documented default row-major order is enforced > throughout the library with a series of `order='C'` default parameters, so > given this I supposed there's no way to change the default (or am I wrong?) > If, supposedly, I'd change that by patching the library (substituting 'C's > for 'F's), do you think there would by any problem with other downstream > libraries using numpy in my project? Do you think they assume a > default-constructed array is always row-major and access the underlying > data? > _______________________________________________ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: kevin.k.shepp...@gmail.com >
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
