Re: [Numpy-discussion] Attribute hiding APIs for PyArrayObject

It's probably helpful to know that Py_LIMITED_API is a kinda-experimental thing that was added in CPython 3.2 (see PEP 384) and remains almost 100% unused. It has never been a popular or influential thing (for better or worse). -n On Tue, Oct 30, 2018 at 6:41 PM, Eric Wieser wrote: > In NumPy 1.

Re: [Numpy-discussion] Attribute hiding APIs for PyArrayObject

In NumPy 1.14 we changed UPDATEIFCOPY to WRITEBACKIFCOPY, and in 1.16 we would like to deprecate PyArray_SetNumericOps and PyArray_GetNumericOps. The strange warning when NPY_NO_DEPRICATED_API is annoying I’m not sure I make the connection here between hidden fields and API deprecation. You seem t

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

On Tue, 30 Oct 2018 23:56:17 +0100, Hameer Abbasi wrote: > I meant we should have a calendar that’s possible to subscribe to, and > in addition announce the agenda here, and that the calendar could > contain a link to the meeting agenda. Here you go: https://calendar.google.com/calendar?cid=YmVya

Re: [Numpy-discussion] asanyarray vs. asarray

Would the extended dtypes also violate the Liskov substitution principle? In place operations which would mutate the dtype are one potential issue. Would a single dtype for an array be sufficient, i.e. np.polynomial coefficients? Compared to ndarray subclasses, the memory layout issue goes away, b

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

Hi, I meant we should have a calendar that’s possible to subscribe to, and in addition announce the agenda here, and that the calendar could contain a link to the meeting agenda. Best Regards, Hameer Abbasi > On Tuesday, Oct 30, 2018 at 11:52 PM, Stefan van der Walt > mailto:stef...@berkeley.

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

Hi Hameer, On Tue, 30 Oct 2018 21:24:36 +0100, Hameer Abbasi wrote: > If I may make a suggestion, it might be nice to create a separate > calendar and add people to it as needed for better management. Can you clarify what you want? Do you mean we should not announce the meeting agenda here, and

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

I'll try to make it, but can't guarantee. The last time there was discussion of the structured-array PRs which are currently held up, and I sort of promised to have a writeup of the issues. I put up a draft of that here: https://gist.github.com/ahaldane/6cd44886efb449f9c8d5ea012747323b Alla

Re: [Numpy-discussion] asanyarray vs. asarray

On Tue, Oct 30, 2018 at 2:22 PM, Stephan Hoyer wrote: > The Liskov substitution principle (LSP) suggests that the set of > reasonable ndarray subclasses are exactly those that could also in > principle correspond to a new dtype. Of np.ndarray subclasses in > wide-spread use, I think only the vari

Re: [Numpy-discussion] asanyarray vs. asarray

On Mon, Oct 29, 2018 at 9:49 PM Eric Wieser wrote: > The latter - changing the behavior of multiplication breaks the principle. > > But this is not the main reason for deprecating matrix - almost all of the > problems I’ve seen have been caused by the way that matrices behave when > sliced. The w

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

Hello! If I may make a suggestion, it might be nice to create a separate calendar and add people to it as needed for better management. Best Regards, Hameer Abbasi > On Tuesday, Oct 30, 2018 at 8:16 PM, Matti Picus (mailto:matti.pi...@gmail.com)> wrote: > > The draft agenda is at https://hackm

[Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

The draft agenda is at https://hackmd.io/D3I3CdO2T9ipZ2g5uAChcA?both. Everyone is invited to join. Matti, Tyler and Stefan ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/ma

[Numpy-discussion] NumPy 1.15.4 release

Hi All, Just a heads up that I am planning on making a 1.15.4 release this coming weekend. The only fixes planned at this point are - BUG: Fix fill value in masked array '==' and '!=' ops, #12257 - BUG: clear buffer_info_cache on scalar dealloc

Re: [Numpy-discussion] Depreciating asfortranarray and ascontiguousarray

On Sat, 2018-10-27 at 19:29 +1300, Ralf Gommers wrote: > > > On Sat, Oct 27, 2018 at 6:37 PM Eric Wieser < > wieser.eric+nu...@gmail.com> wrote: > > > in order to be used prior to calling C or Fortran code that > > > expected at least a 1-d array > > > > > > > > > > I'm a big supporter of m

Re: [Numpy-discussion] asanyarray vs. asarray

On Tue, Oct 30, 2018 at 12:49 AM Eric Wieser wrote: > The latter - changing the behavior of multiplication breaks the principle. > > But this is not the main reason for deprecating matrix - almost all of the > problems I’ve seen have been caused by the way that matrices behave when > sliced. The

[Numpy-discussion] einops 0.1

Dear numpy community, I'm happy to announce the first public release of einops package.einops is a new way to manipulate tensors. Examples with numpy worth a thousand words:https://github.com/arogozhnikov/einops/blob/master/docs/1-einops-basics.ipynb einops introduces a special notation which inclu

[Numpy-discussion] Attribute hiding APIs for PyArrayObject

TL;DR - should we revert the attribute-hiding constructs in ndarraytypes.h and unify PyArrayObject_fields with PyArrayObject? Background NumPy 1.8 deprecated direct access to PyArrayObject fields. It made PyArrayObject "opaque", and hid the fields behind a PyArrayObject_fields structure ht