On Thu, Nov 9, 2017 at 12:15 PM, Nathaniel Smith wrote:
> On Nov 8, 2017 16:51, "Matthew Brett" wrote:
>
> Hi,
>
> On Wed, Nov 8, 2017 at 7:08 PM, Julian Taylor
> wrote:
> > On 06.11.2017 11:10, Ralf Gommers wrote:
> >>
> >>
> >> On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
> >> mailto:char
On Wed, Nov 8, 2017 at 10:17 PM, Bryan Van de ven wrote:
>
>> On Nov 8, 2017, at 10:50, Peter Cock wrote:
>>
>> NumPy (and to a lesser extent SciPy) is in a tough position being at the
>> bottom of many scientific Python programming stacks. Whenever you
>> drop Python 2 support is going to upset
On Nov 8, 2017 16:51, "Matthew Brett" wrote:
Hi,
On Wed, Nov 8, 2017 at 7:08 PM, Julian Taylor
wrote:
> On 06.11.2017 11:10, Ralf Gommers wrote:
>>
>>
>> On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
>> mailto:charlesr.har...@gmail.com>> wrote:
>>
>> Hi All,
>>
>> Thought I'd toss th
Hi,
On Wed, Nov 8, 2017 at 7:08 PM, Julian Taylor
wrote:
> On 06.11.2017 11:10, Ralf Gommers wrote:
>>
>>
>> On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
>> mailto:charlesr.har...@gmail.com>> wrote:
>>
>> Hi All,
>>
>> Thought I'd toss this out there. I'm tending towards better sooner
Anaconda's compilers are for Linux (gcc 7.2) and Mac (llvm/clang 4.0.1)
right now. We would like to have clang target all platforms, but that's a
lot of development effort.
We are also exploring ways of keeping package ecosystems in line, so that
building and managing a self-consistent set of pyt
> On Nov 8, 2017, at 10:50, Peter Cock wrote:
>
> NumPy (and to a lesser extent SciPy) is in a tough position being at the
> bottom of many scientific Python programming stacks. Whenever you
> drop Python 2 support is going to upset someone.
Existing versions of NumPy will still exist and conti
On 11/08/2017 03:12 PM, Nathaniel Smith wrote:
> - We could adjust the API so that there's some explicit operation to
> trigger the final writeback. At the Python level this would probably
> mean that we start supporting the use of nditer as a context manager,
> and eventually start raising an erro
On Wed, Nov 8, 2017 at 11:08 AM, Julian Taylor <
jtaylor.deb...@googlemail.com> wrote:
>
> Would dropping python2 support for windows earlier than the other
> platforms a reasonable approach?
>
no. I'm not Windows fan myself, but it is a HUGE fraction of the userbase.
-CHB
--
Christopher Bar
At a higher level:
The issue here is that we need to break the nditer API. This might
affect you if you np.nditer (in Python) or the NpyIter_* APIs (in C).
The exact cases affected are somewhat hard to describe because
nditer's flag processing is complicated [1], but basically it's cases
where you
On 06.11.2017 11:10, Ralf Gommers wrote:
>
>
> On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
> mailto:charlesr.har...@gmail.com>> 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 starti
On Wed, 2017-11-08 at 18:15 +0100, Ilhan Polat wrote:
> I was about to send the same thing. I think this matter became a
> vim/emacs issue and Py2 supporters won't take any arguments anymore.
> But if Instagram can do it, it means that legacy code argument is a
> matter of will but not a technicali
Date: Wed, 8 Nov 2017 18:41:03 +0200
From: Matti Picus
To: numpy-discussion@python.org
Subject: [Numpy-discussion] deprecate updateifcopy in nditer operand
flags?
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed
I filed issue 9714 https://github.com/nump
I was about to send the same thing. I think this matter became a vim/emacs
issue and Py2 supporters won't take any arguments anymore. But if Instagram
can do it, it means that legacy code argument is a matter of will but not a
technicality. https://thenewstack.io/instagram-makes-smooth-move-python-
On Tue, Nov 7, 2017 at 11:40 PM, Nathaniel Smith wrote:
>
>
>
> Right now, the decision in front of us is what to tell people who ask about
> numpy's py2 support plans, so that they can make their own plans. Given what
> we know right now, I don't think we should promise to keep support past
> 20
I filed issue 9714 https://github.com/numpy/numpy/issues/9714 and wrote
a mail in September trying to get some feedback on what to do with
updateifcopy semantics and user-exposed nditer.
It garnered no response, so I am trying again.
For those who are unfamiliar with the issue see below for a sh
15 matches
Mail list logo
