On Mon, Nov 6, 2017 at 6:37 PM, David Cournapeau wrote:
>
>
> On Tue, Nov 7, 2017 at 7:24 AM, Chris Barker
> wrote:
>
>> On Sun, Nov 5, 2017 at 10:25 AM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>
>>> the timeline I've been playing
On Tue, Nov 7, 2017 at 7:24 AM, Chris Barker wrote:
> On Sun, Nov 5, 2017 at 10:25 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>
>> the timeline I've been playing with is to keep Python 2.7 support
>> through 2018, which given our current pace, would be
On Mon, Nov 6, 2017 at 3:18 PM, Chris Barker wrote:
> Klunky, and maybe we could come up with a standard way to do it and
> include that in numpy, but I'm not sure that ABCs are the way to do it.
>
ABCs are *absolutely* the way to go about it. It's the only way baked into
On Sun, Nov 5, 2017 at 10:25 AM, Charles R Harris wrote:
> the timeline I've been playing with is to keep Python 2.7 support through
> 2018, which given our current pace, would be for NumPy 1.15 and 1.16. After
> that 1.16 would become a long term support release
On Sat, Nov 4, 2017 at 6:47 AM, Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
>
> You just summarized excellently why I'm on a quest to change `asarray`
> to `asanyarray` within numpy
+1 -- we should all be using asanyarray() most of the time. However a
couple notes:
asarray()
On 04/11/17 18:00,
numpy-discussion-requ...@python.org wrote:
Date: Fri, 3 Nov 2017 20:56:38 -0600
From: Charles R Harris
To: numpy-discussion
Subject: [Numpy-discussion] NumPy 1.14 branch.
On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
wrote:
> Hi All,
>
> Thought I'd toss this out there. I'm tending towards better sooner than
> later in dropping Python 2.7 support as we are starting to run up against
> places where we would like to use Python 3