[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

2022-05-03 Thread Sebastian Berg
Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, May 4th at 16:00 UTC (9:00am Pacific Time). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

[Numpy-discussion] Re: NumPy Development Meeting Wednesday - Triage Focus

2022-05-03 Thread Renato Fabbri
On Tue, May 3, 2022 at 1:48 PM Sebastian Berg wrote: > Hi all, > > Our bi-weekly triage-focused NumPy development meeting is Wednesday, > May 4th at 16:00 UTC (9:00am Pacific Time). > Everyone is invited to join in and edit the work-in-progress meeting > topics and notes: > https://hackmd.io/68i_

[Numpy-discussion] Numpy-related jobs, grants, etc

2022-05-03 Thread Renato Fabbri
This is not only for me, but a question for the community in general. Do we have an open knowledge base of budget (interested companies or individuals, public funding) for developing numpy-related packages? Explaining a bit with a specific case... In the last few years, I have many times thought a

[Numpy-discussion] Re: Types in pure Python sources

2022-05-03 Thread Ralf Gommers
On Sun, May 1, 2022 at 9:08 PM Sergei Lebedev wrote: > > I think that's on purpose, because the type annotations are quite > complex. > > For reasons of correctness/completeleness, they use protocols, mixins, > and > > overloads. Inside pure Python code, that would be harder to read and > > maint

[Numpy-discussion] Re: Types in pure Python sources

2022-05-03 Thread bas van beek
I share Ralf’s general sentiment here; the abundance of overloads makes it in my opinion undesirable to move to inline annotations due the sheer amount of extra clutter. This is in part due to dtype-typing support, which is currently difficult to express without overloads, though I do expect th

[Numpy-discussion] Discussion: History & Possible Deprecation/Removal of numpy.linalg.{eig(), eigvals()}?

2022-05-03 Thread Leo Fang
Hi, I am catching up with an assigned task that I slipped. I am wondering a few things about the numpy.linalg.eig() API (eigvals() is also included in this discussion, but for simplicity let's focus on eig()). AFAIU the purpose of eig() is for handling general eigen-systems which have left and r

[Numpy-discussion] Re: Discussion: History & Possible Deprecation/Removal of numpy.linalg.{eig(), eigvals()}?

2022-05-03 Thread Charles R Harris
On Tue, May 3, 2022 at 6:41 PM Leo Fang wrote: > Hi, I am catching up with an assigned task that I slipped. I am wondering > a few things about the numpy.linalg.eig() API (eigvals() is also included > in this discussion, but for simplicity let's focus on eig()). AFAIU the > purpose of eig() is fo

[Numpy-discussion] Re: Discussion: History & Possible Deprecation/Removal of numpy.linalg.{eig(), eigvals()}?

2022-05-03 Thread Robert Kern
On Tue, May 3, 2022 at 8:40 PM Leo Fang wrote: > Hi, I am catching up with an assigned task that I slipped. I am wondering > a few things about the numpy.linalg.eig() API (eigvals() is also included > in this discussion, but for simplicity let's focus on eig()). AFAIU the > purpose of eig() is fo