On Wed, Dec 17, 2014 at 3:26 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Sun, Dec 14, 2014 at 6:47 PM, Jaime Fernández del Río < jaime.frio@gmail.com> wrote:
On Sun, Dec 14, 2014 at 2:02 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Sat, Dec 13, 2014 at 10:22 PM, Daπid <davidmenhur@gmail.com> wrote:
On 13 December 2014 at 13:34, Lars Buitinck <larsmans@gmail.com> wrote:
I don't, but I just checked the NumPy version that comes with various Linux distros so we can see what people are likely to have. There is no Ubuntu long-term support release that ships 1.5, only 1.4 (10.04) or 1.6 (12.04) [1]. Debian doesn't list 1.5 for any of its releases either [2]. CentOS 6 ships 1.4 [3], while CentOS 7 ships 1.7.1 [4].
Thanks for checking. The most recent Ubuntu LTS and CentOS releases are good data points in general I'd say. In this case Ubuntu (and Debian stable) are on 1.6.x, so keep that but drop 1.5.x then?
+1 on dropping 1.5.x.
I would actually skip over 1.6 and go all the way to 1.7 and its multi-axis reduction operations. But having einsum and out kwargs is already a much welcome change.
Summary of this thread so far: everyone in favor of dropping 1.5.x support, on keeping 1.6.x support the opinions are a bit more mixed. So I propose that we go ahead and drop 1.5.x (let's consider it final if no one objects in the next day or two) and reconsider dropping 1.6.x in the next release cycle.
I'd actually suggest only supporting 1.6.2 - no use trying to work around bugs in 1.6.0/1.6.1 that have been fixed. We did the same with 1.5.x.
+1 Warren
Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev