On Wed, Nov 4, 2020 at 7:22 PM Aaron Meurer wrote:
>
> > That's not to say that there isn't clearer language that could be
> drafted. The NEP is still in Draft stage. But if you think it could be
> clearer, please propose specific edits to the draft. Like with unclear
> documentation, it's the pe
On Wed, Nov 4, 2020, at 16:21, Aaron Meurer wrote:
> But as I noted, this is already off topic for the original discussion
> here, and since there's apparently no interest in improving the NEP
> wording, I'll drop it.
I was trying to understand where, specifically, the language falls short, and
w
> Misinterpreted in what way? That they would think we have an ability to
> enforce the guidelines? We *are* trying to encourage certain behavior here.
> If they read it and, our of abundant caution reach out to us, that's a fine
> outcome.
> What negative outcomes do you foresee?
That it is a
On Wed, Nov 4, 2020 at 5:55 PM Aaron Meurer wrote:
> On Wed, Nov 4, 2020 at 3:02 PM Robert Kern wrote:
> >
> > On Wed, Nov 4, 2020 at 4:49 PM Aaron Meurer wrote:
> >>
> >> I hope this isn't too off topic, but this "fair play" NEP reads like
> >> it is a set of additional restrictions on the Num
On Wed, Nov 4, 2020, at 14:54, Aaron Meurer wrote:
> Again, *I* understand the purpose of this document, but I think the
> way it is currently written it could easily be misinterpreted by
> someone else.
Misinterpreted in what way? That they would think we have an ability to enforce
the guideline
On Wed, Nov 4, 2020 at 3:02 PM Robert Kern wrote:
>
> On Wed, Nov 4, 2020 at 4:49 PM Aaron Meurer wrote:
>>
>> I hope this isn't too off topic, but this "fair play" NEP reads like
>> it is a set of additional restrictions on the NumPy license, which if
>> it is, would make NumPy no longer open so
On Wed, Nov 4, 2020, at 13:47, Aaron Meurer wrote:
> I hope this isn't too off topic, but this "fair play" NEP reads like
> it is a set of additional restrictions on the NumPy license, which if
> it is, would make NumPy no longer open source by the OSI definition. I
> think the NEP should be much c
On Tue, 2020-11-03 at 17:54 +0200, Matti Picus wrote:
> Hi. On behalf of Quansight and RTOSHoldings, I would like to
> introduce
> "pnumpy", a package to speed up NumPy.
>
> https://quansight.github.io/numpy-threading-extensions/stable/index.html
>
Nice to see these efforts especially with inte
On Wed, Nov 4, 2020 at 4:49 PM Aaron Meurer wrote:
> I hope this isn't too off topic, but this "fair play" NEP reads like
> it is a set of additional restrictions on the NumPy license, which if
> it is, would make NumPy no longer open source by the OSI definition. I
> think the NEP should be much
I hope this isn't too off topic, but this "fair play" NEP reads like
it is a set of additional restrictions on the NumPy license, which if
it is, would make NumPy no longer open source by the OSI definition. I
think the NEP should be much clearer that these are requests but not
requirements.
Aaron
On Tue, Nov 3, 2020 at 3:54 PM Matti Picus wrote:
> Hi. On behalf of Quansight and RTOSHoldings, I would like to introduce
> "pnumpy", a package to speed up NumPy.
>
> https://quansight.github.io/numpy-threading-extensions/stable/index.html
>
>
> What is in it?
>
> - use "PyUFunc_ReplaceLoopBySig
Hi. On behalf of Quansight and RTOSHoldings, I would like to introduce
"pnumpy", a package to speed up NumPy.
https://quansight.github.io/numpy-threading-extensions/stable/index.html
What is in it?
- use "PyUFunc_ReplaceLoopBySignature" to hook all the UFunc inner loops
- When the inner loop
12 matches
Mail list logo
