On Sun, Feb 23, 2020 at 3:59 PM Ralf Gommers wrote:
>
>
> On Sun, Feb 23, 2020 at 3:31 PM Stephan Hoyer wrote:
>
>> On Thu, Feb 6, 2020 at 12:20 PM Sebastian Berg <
>> sebast...@sipsolutions.net> wrote:
>>
>>>
>>> Another thing about backward compatibility: What is our vision there
>>> actually?
On Sun, Feb 23, 2020 at 3:31 PM Stephan Hoyer wrote:
> On Thu, Feb 6, 2020 at 12:20 PM Sebastian Berg
> wrote:
>
>>
>> Another thing about backward compatibility: What is our vision there
>> actually?
>> This NEP will *not* give the *end user* the option to opt-in! Here,
>> opt-in is really rese
On Thu, Feb 6, 2020 at 12:20 PM Sebastian Berg
wrote:
> > It is less clear how this could work for __array_module__, because
>
> __array_module__ and get_array_module() are not generic -- they
> > refers explicitly to a NumPy like module. If we want to extend it to
> > SciPy (for which I agree th
On Sat, 2020-02-22 at 13:28 -0800, Nathaniel Smith wrote:
> Off the cuff, my intuition is that dtypes will want to be able to
> define how scalar indexing works, and let it return objects other
> than
> arrays. So e.g.:
>
> - some dtypes might just return a zero-d array
> - some dtypes might want
Hi, Sebastian,
On 22.02.20, 02:37, "NumPy-Discussion on behalf of Sebastian Berg"
wrote:
Hi all,
When we create new datatypes, we have the option to make new choices
for the new datatypes [0] (not the existing ones).
The question is: Should every NumPy datatype have a
