Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

2017-11-06 Thread Charles R Harris
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 with is to keep Python 2.7 support >>> throu

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

2017-11-06 Thread David Cournapeau
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 for NumPy 1.15 and >> 1.1

Re: [Numpy-discussion] is __array_ufunc__ ready for prime-time?

2017-11-06 Thread Stephan Hoyer
On Mon, Nov 6, 2017 at 2:29 PM Ryan May wrote: > 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 ab

Re: [Numpy-discussion] is __array_ufunc__ ready for prime-time?

2017-11-06 Thread Ryan May
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 the Python language its

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

2017-11-06 Thread Chris Barker
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 with backports of > critical bu

Re: [Numpy-discussion] is __array_ufunc__ ready for prime-time?

2017-11-06 Thread Chris Barker
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() pre-dat

Re: [Numpy-discussion] NumPy-Discussion Digest, Vol 134, Issue 10

2017-11-06 Thread Matti Picus
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. Message-ID: Content-Type: text/plain; charset="utf-8" Hi All,

Re: [Numpy-discussion] NumPy 1.14 branch.

2017-11-06 Thread Charles R Harris
On Mon, Nov 6, 2017 at 2:56 AM, Ralf Gommers wrote: > > > On Sat, Nov 4, 2017 at 3:56 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> I'd like to branch NumPy 1.14 soon. >> > > Sounds good. > > Before doing so, I'd like to make sure at a minimum that >> >> 1) Changes

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

2017-11-06 Thread Ralf Gommers
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 features. That is particularly > t

Re: [Numpy-discussion] NumPy 1.14 branch.

2017-11-06 Thread Ralf Gommers
On Sat, Nov 4, 2017 at 3:56 PM, Charles R Harris wrote: > Hi All, > > I'd like to branch NumPy 1.14 soon. > Sounds good. Before doing so, I'd like to make sure at a minimum that > > 1) Changes in array print formatting are done. > 2) Proposed deprecations have been make. > > If there are other