Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Stephan Hoyer
alt > > Sent: Thursday, March 7, 2019 12:15 PM > > To: Discussion of Numerical Python > > Cc: Matthew Rocklin > > Subject: Re: [Numpy-discussion] NEP-18 comment > > > > Hi Sebastian, Frederic, > > > > On Thu, 07 Mar 2019 14:23:10 +, Frederi

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Sebastian Berg
t: Thursday, March 7, 2019 12:15 PM > To: Discussion of Numerical Python > Cc: Matthew Rocklin > Subject: Re: [Numpy-discussion] NEP-18 comment > > Hi Sebastian, Frederic, > > On Thu, 07 Mar 2019 14:23:10 +, Frederic Bastien wrote: > > I like your idea Sebastian. This

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Marten van Kerkwijk
> > Did I miss something? > > Frédéric > > -Original Message- > From: NumPy-Discussion nvidia@python.org> On Behalf Of Stefan van der Walt > Sent: Thursday, March 7, 2019 12:15 PM > To: Discussion of Numerical Python > Cc: Matthew Rocklin > Subject: Re: [Nump

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Frederic Bastien
Of Stefan van der Walt Sent: Thursday, March 7, 2019 12:15 PM To: Discussion of Numerical Python Cc: Matthew Rocklin Subject: Re: [Numpy-discussion] NEP-18 comment Hi Sebastian, Frederic, On Thu, 07 Mar 2019 14:23:10 +, Frederic Bastien wrote: > I like your idea Sebastian. This way it is enab

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Stefan van der Walt
Hi Sebastian, Frederic, On Thu, 07 Mar 2019 14:23:10 +, Frederic Bastien wrote: > I like your idea Sebastian. This way it is enabled only when needed and it is > invisible to the user at the same time. > > Stefan, does it solve well enough the potential problem you raised? I don't think

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Frederic Bastien
-Original Message- From: NumPy-Discussion On Behalf Of Sebastian Berg Sent: Thursday, March 7, 2019 8:58 AM To: numpy-discussion@python.org Subject: Re: [Numpy-discussion] NEP-18 comment On Wed, 2019-03-06 at 12:41 -0800, Stephan Hoyer wrote: > On Wed, Mar 6, 2019 at 10:10 AM Frede

Re: [Numpy-discussion] NEP-18 comment

2019-03-07 Thread Sebastian Berg
On Wed, 2019-03-06 at 12:41 -0800, Stephan Hoyer wrote: > On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien > wrote: > > Hi, > > > > I was told recently about the NEP-18. I like it, but I have a > > comment. > > > > At first, it is enabled in a release by setting an environment > > variable. >

Re: [Numpy-discussion] NEP-18 comment

2019-03-06 Thread Stefan van der Walt
It's great to have your input here, Frederic—thank you! On Wed, 06 Mar 2019 12:41:11 -0800, Stephan Hoyer wrote: > I agree, this seems like an easy and worthwhile change. The NEP-18 > implementation has been rewritten in C, so I expect that the typical > overhead will be quite minimal (about 1 us

Re: [Numpy-discussion] NEP-18 comment

2019-03-06 Thread Frederic Bastien
could be wrong on that. I’m too close to machine learning/deep learning to evaluation well that point. From: NumPy-Discussion On Behalf Of Stephan Hoyer Sent: Wednesday, March 6, 2019 3:41 PM To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] NEP-18 comment On Wed, Mar 6

Re: [Numpy-discussion] NEP-18 comment

2019-03-06 Thread Stephan Hoyer
On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien wrote: > Hi, > > > > I was told recently about the NEP-18. I like it, but I have a comment. > > > > At first, it is enabled in a release by setting an environment variable. > > Then in the following release, it is enabled by default. > > > > Is it

[Numpy-discussion] NEP-18 comment

2019-03-06 Thread Frederic Bastien
Hi, I was told recently about the NEP-18. I like it, but I have a comment. At first, it is enabled in a release by setting an environment variable. Then in the following release, it is enabled by default. Is it possible to allow for the second release to disable it by an environment variable?