On Tue, Nov 6, 2018 at 8:09 PM Stephan Hoyer wrote:
> On Tue, Nov 6, 2018 at 6:08 PM Stefan van der Walt
> wrote:
>
>> On Sun, 04 Nov 2018 17:16:12 -0800, Stephan Hoyer wrote:
>> > On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk <
>> > m.h.vankerkw...@gmail.com> wrote:
>> >
>> > > For `__arr
On Tue, Nov 6, 2018 at 6:08 PM Stefan van der Walt
wrote:
> On Sun, 04 Nov 2018 17:16:12 -0800, Stephan Hoyer wrote:
> > On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk <
> > m.h.vankerkw...@gmail.com> wrote:
> >
> > > For `__array_function__`, there was some discussion in
> > > https://githu
On Sun, 04 Nov 2018 17:16:12 -0800, Stephan Hoyer wrote:
> On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk <
> m.h.vankerkw...@gmail.com> wrote:
>
> > For `__array_function__`, there was some discussion in
> > https://github.com/numpy/numpy/issues/12225 that for 1.16 we might want
> > to follo
For astropy, we also waiting a little before having a rip-python2-out
fiesta.
I think it is worth trying to get matmul in 1.16, independently of
__array_function__ - it really belongs to ufunc overwrites and all the
groundwork has been done.
For __array_function__, is it at all an option to go to
> Thoughts on how to proceed are welcome.
I've been involved in scikit-image and that project tore out the python2
only code rather quickly after 2.7 support was dropped. I think it caused a
few hiccups when backporting bugfixes. I imagine that `1.16.1` and `1.16.2`
releases will come out quickly
On Sun, Nov 4, 2018 at 6:16 PM Stephan Hoyer wrote:
> On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk <
> m.h.vankerkw...@gmail.com> wrote:
>
>> Hi Chuck,
>>
>> For `__array_function__`, there was some discussion in
>> https://github.com/numpy/numpy/issues/12225 that for 1.16 we might want
>>
On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Hi Chuck,
>
> For `__array_function__`, there was some discussion in
> https://github.com/numpy/numpy/issues/12225 that for 1.16 we might want
> to follow after all Nathaniel's suggestion of using an environm
On 4/11/18 8:04 pm, Charles R Harris wrote:
Hi All,
Time to begin looking forward to the NumPy 1.16.x branch. I think
there are three main topics to address:
1. current PRs that need review and merging,
2. critical fixes that need to be made,
3. status of `__array_function__`.
The last
Hi Chuck,
For `__array_function__`, there was some discussion in
https://github.com/numpy/numpy/issues/12225 that for 1.16 we might want to
follow after all Nathaniel's suggestion of using an environment variable or
so to opt in (since introspection breaks on python2 with our wrapped
implementatio
Hi All,
Time to begin looking forward to the NumPy 1.16.x branch. I think there are
three main topics to address:
1. current PRs that need review and merging,
2. critical fixes that need to be made,
3. status of `__array_function__`.
The last probably needs some discussion. `__array_fu
10 matches
Mail list logo
