On Fri, Aug 24, 2018 at 3:14 PM Nathaniel Smith wrote:
> Yeah, the reason warnings are normally recommended is because
> normally, you want to make it easy to silence. But this is the rare
> case where I didn't want to make it easy to silence, so I didn't
> suggest using a warning :-).
>
> Callin
> I’m On 25. Aug 2018, at 00:13, Nathaniel Smith wrote:
>
>> On Fri, Aug 24, 2018 at 1:46 PM, Stephan Hoyer wrote:
>> On Fri, Aug 24, 2018 at 1:36 AM Hameer Abbasi
>> wrote:
>>>
>>>
On Fri, Aug 24, 2018 at 9:38 AM Nathaniel Smith wrote:
> On Thu, Aug 23, 2018 at 9:02 AM, wro
On Fri, Aug 24, 2018 at 1:46 PM, Stephan Hoyer wrote:
> On Fri, Aug 24, 2018 at 1:36 AM Hameer Abbasi
> wrote:
>>
>>
>> On Fri, Aug 24, 2018 at 9:38 AM Nathaniel Smith wrote:
>>>
>>> On Thu, Aug 23, 2018 at 9:02 AM, wrote:
>>> > I might add that most duck array authors are highly unlikely to b
On Fri, Aug 24, 2018 at 1:36 AM Hameer Abbasi
wrote:
>
> On Fri, Aug 24, 2018 at 9:38 AM Nathaniel Smith wrote:
>
>> On Thu, Aug 23, 2018 at 9:02 AM, wrote:
>> > I might add that most duck array authors are highly unlikely to be
>> newcomers
>> > to the Python space. We should just put a big w
On Fri, Aug 24, 2018, 09:07 Hameer Abbasi wrote:
>
>
> On Fri, Aug 24, 2018 at 5:55 PM Stephan Hoyer wrote:
>
>> On Thu, Aug 23, 2018 at 1:06 PM Hameer Abbasi
>> wrote:
>>
>>> I might add that if it’s a mandatory part of the protocol, then not all
>>> things will work. For example, if XArray an
On Fri, Aug 24, 2018 at 5:55 PM Stephan Hoyer wrote:
> On Thu, Aug 23, 2018 at 1:06 PM Hameer Abbasi
> wrote:
>
>> I might add that if it’s a mandatory part of the protocol, then not all
>> things will work. For example, if XArray and Dask want to support sparse
>> arrays, they’ll need to add an
On Thu, Aug 23, 2018 at 1:06 PM Hameer Abbasi
wrote:
> I might add that if it’s a mandatory part of the protocol, then not all
> things will work. For example, if XArray and Dask want to support sparse
> arrays, they’ll need to add an explicit dependency.
>
I don't follow -- can you please elabo
Hi everyone,
On Fri, Aug 24, 2018 at 9:38 AM Nathaniel Smith wrote:
> On Thu, Aug 23, 2018 at 9:02 AM, wrote:
> > I might add that most duck array authors are highly unlikely to be
> newcomers
> > to the Python space. We should just put a big warning there while
> enabling
> > and that’ll be e
On Thu, Aug 23, 2018 at 9:02 AM, wrote:
> I might add that most duck array authors are highly unlikely to be newcomers
> to the Python space. We should just put a big warning there while enabling
> and that’ll be enough to scare away most devs from doing it by default.
That's a reasonable idea..
