On Mon, Jun 11, 2012 at 12:03 AM, James Bergstra
wrote:
> If anyone is interested in my ongoing API & bytecode adventure in why
> / how lazy computing could be useful, I've put together a few tiny
> hypothetically-runnable examples here:
>
> https://github.com/jaberg/numba/tree/master/examples
> h
Hi all, (sorry for missing the debate, I don't often check my
numpy-list folder.)
I agree that an "official" numpy solution to this problem is
premature, but at the same time I think the failure to approach
anything remotely resembling a consensus on how to deal with lazy
evaluation is really gumm
On 06/06/2012 12:06 AM, mark florisson wrote:
> On 5 June 2012 22:36, Dag Sverre Seljebotn wrote:
>> On 06/05/2012 10:47 PM, mark florisson wrote:
>>> On 5 June 2012 20:17, Nathaniel Smithwrote:
On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
wrote:
> On 5 June 2012 17:38, Nat
On 5 June 2012 22:36, Dag Sverre Seljebotn wrote:
> On 06/05/2012 10:47 PM, mark florisson wrote:
>> On 5 June 2012 20:17, Nathaniel Smith wrote:
>>> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
>>> wrote:
On 5 June 2012 17:38, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 4:12 PM
On 5 June 2012 22:29, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 9:47 PM, mark florisson
> wrote:
>> On 5 June 2012 20:17, Nathaniel Smith wrote:
>>> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
>>> wrote:
On 5 June 2012 17:38, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 4:
On 06/05/2012 10:47 PM, mark florisson wrote:
> On 5 June 2012 20:17, Nathaniel Smith wrote:
>> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
>> wrote:
>>> On 5 June 2012 17:38, Nathaniel Smith wrote:
On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
wrote:
> On 5 June 2012 14:58,
On Tue, Jun 5, 2012 at 9:47 PM, mark florisson
wrote:
> On 5 June 2012 20:17, Nathaniel Smith wrote:
>> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
>> wrote:
>>> On 5 June 2012 17:38, Nathaniel Smith wrote:
On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
wrote:
> On 5 June 2012
On 5 June 2012 20:17, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
> wrote:
>> On 5 June 2012 17:38, Nathaniel Smith wrote:
>>> On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
>>> wrote:
On 5 June 2012 14:58, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 12
On Tue, Jun 5, 2012 at 7:08 PM, mark florisson
wrote:
> On 5 June 2012 17:38, Nathaniel Smith wrote:
>> On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
>> wrote:
>>> On 5 June 2012 14:58, Nathaniel Smith wrote:
On Tue, Jun 5, 2012 at 12:55 PM, mark florisson
wrote:
> It would be g
On 5 June 2012 17:38, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
> wrote:
>> On 5 June 2012 14:58, Nathaniel Smith wrote:
>>> On Tue, Jun 5, 2012 at 12:55 PM, mark florisson
>>> wrote:
It would be great if we implement the NEP listed above, but with a few
On 5 June 2012 18:21, Neal Becker wrote:
> Would lazy eval be able to eliminate temps in doing operations such as:
>
> np.sum (u != 23)?
>
> That is, now ops involving selecting elements of matrixes are often performed
> by
> first constructing temp matrixes, and the operating on them.
>
> __
Would lazy eval be able to eliminate temps in doing operations such as:
np.sum (u != 23)?
That is, now ops involving selecting elements of matrixes are often performed
by
first constructing temp matrixes, and the operating on them.
___
NumPy-Discussi
On Tue, Jun 5, 2012 at 4:12 PM, mark florisson
wrote:
> On 5 June 2012 14:58, Nathaniel Smith wrote:
>> On Tue, Jun 5, 2012 at 12:55 PM, mark florisson
>> wrote:
>>> It would be great if we implement the NEP listed above, but with a few
>>> extensions. I think Numpy should handle the lazy evalua
On 5 June 2012 14:58, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 12:55 PM, mark florisson
> wrote:
>> It would be great if we implement the NEP listed above, but with a few
>> extensions. I think Numpy should handle the lazy evaluation part, and
>> determine when expressions should be evalua
On Tue, Jun 5, 2012 at 12:55 PM, mark florisson
wrote:
> It would be great if we implement the NEP listed above, but with a few
> extensions. I think Numpy should handle the lazy evaluation part, and
> determine when expressions should be evaluated, etc. However, for each
> user operation, Numpy w
Hey,
Another discussion on lazy evaluation, given the recent activity here:
https://github.com/ContinuumIO/numba/pull/6#issuecomment-6117091
A somewhat recent previous thread can be found here:
http://mail.scipy.org/pipermail/numpy-discussion/2012-February/060862.html
, and a NEP here:
https://git
16 matches
Mail list logo