High level abstractions like .flat or boolean indexing / np.nonzero()
always use C ordering regardless of the underlying data.
>>> list(np.asarray([[0, 1], [2, 3]]).flat)
[0, 1, 2, 3]
>>> list(np.asarray([[0, 1], [2, 3]], order='F').flat)
[0, 1, 2, 3]
C and Fortran ordering are really just specia
Charles R Harris
Sat, Oct 14, 3:03 PM
to numpy-discussion, SciPy, bcc: python-announce-list
Hi All,
On behalf of the NumPy team, I'm pleased to announce the release of NumPy
1.26.2. NumPy 1.26.2 is a maintenance release that fixes bugs and
regressions discovered after the 1.26.1 release. The Pyth
The next NumPy triage meeting will be held this Wednesday, November 15th at
5pm UTC. This is a meeting where we synchronously triage prioritized PRs
and issues.
Join us via Zoom:
https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09
.
Everyone is welcome to attend and cont
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 cal
