My memories reappeared:
3. One could think about allowing variable sized .npy files without header
modification at all, e.g. by setting the variable sized shape entry (axis
0) to -1. The length of the array would then be inferred by the file size.
However, what I personally dislike about that appro
Hi,
On Sat, Nov 6, 2021 at 4:54 PM Ralf Gommers wrote:
>
>
>
> On Tue, Oct 26, 2021 at 9:20 PM bas van beek wrote:
>>
>> Hi all,
>>
>>
>>
>> The subject of `MachAr` recently came up in
>> https://github.com/numpy/numpy/pull/20132 and
>>
>> an earlier community meeting, more notably: it’s questi
Great to found from this website such a tremendous blogs. https://bit.ly/3w74pG0
___
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/nump
On Fri, 2021-11-05 at 18:44 -0500, Juan Nunez-Iglesias wrote:
> I agree with the argument to revert. Consistency among libraries should
> be near the top of the list of priorities, as should performance.
> Whether the new behaviour "makes more sense", meanwhile, is debatable.
>
I don't have much
On Sun, 2021-11-07 at 12:36 -0700, Charles R Harris wrote:
> Hi All,
>
> I'd like to propose making the NumPy default pickle protocol 4, the
> same as
> the Python 3.8 default. That would have the advantage of supporting
> large
> pickles. The current default protocol is 2, last the default in
> P
Hi all,
> Am 08.11.2021 um 19:15 schrieb Sebastian Berg :
>
> On Sun, 2021-11-07 at 12:36 -0700, Charles R Harris wrote:
>> Hi All,
>>
>> I'd like to propose making the NumPy default pickle protocol 4, the
>> same as
>> the Python 3.8 default. That would have the advantage of supporting
>> large
I would really like to get my array API PRs in the next release. They
are https://github.com/numpy/numpy/pull/20066 and
https://github.com/numpy/numpy/pull/19980. Currently both require a
few updates from me before they can be merged. I will ping on them
when they are ready. I hope to have them in
