On 14 August 2017 at 16:34, Matthew Brett wrote:
> Hi,
>
> On Fri, Jul 14, 2017 at 1:29 AM, Ralf Gommers wrote:
>>
>>
>> On Fri, Jul 14, 2017 at 8:15 PM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> On Thu, Jul 13, 2017 at
Hi,
On Fri, Jul 14, 2017 at 1:29 AM, Ralf Gommers wrote:
>
>
> On Fri, Jul 14, 2017 at 8:15 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Thu, Jul 13, 2017 at 9:10 AM, Matthew Brett
>> wrote:
>> > Hi,
>> >
>> > On Thu,
On Fri, Jul 14, 2017 at 8:15 PM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Jul 13, 2017 at 9:10 AM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Thu, Jul 13, 2017 at 8:50 AM, Ralf Gommers
> wrote:
> >>
> >>
> >> On Thu, Jul
Hi,
On Thu, Jul 13, 2017 at 9:10 AM, Matthew Brett wrote:
> Hi,
>
> On Thu, Jul 13, 2017 at 8:50 AM, Ralf Gommers wrote:
>>
>>
>> On Thu, Jul 13, 2017 at 6:16 PM, Stefan van der Walt
>> wrote:
>>>
>>> Hi everyone,
>>>
>>>
On 13 July 2017 22:30:03 Nadav Horesh wrote:
I'd make numba dependency optional, since keeping llvm and llvmlite
versions in sync requires special attention (at least with the Linux
distros I used), what makes numba availability below 100%.
I don't think we need to
I'd make numba dependency optional, since keeping llvm and llvmlite
versions in sync requires special attention (at least with the Linux
distros I used), what makes numba availability below 100%.
Nadav.
On Jul 14, 2017 5:23 AM, "Gregory Lee" wrote:
> I am also +1 on
I am also +1 on allowing numba code in scikit-image. I have tended to
prefer Cython in the past, but it has been a while since I looked at numba
and it seems it has come a long way in recent years. Juan's blog post and
the simple example you provided are great examples of relevant use cases.
On Thu, Jul 13, 2017 at 6:16 PM, Stefan van der Walt
wrote:
> Hi everyone,
>
> As many of you know, speed has been a point of contention in
> scikit-image for a long time. We've made a very deliberate decision to
> focus on writing high-level, understandable code (via