I see your time machine is in full working order :-)
--
Travis Oliphant
(on a mobile)
512-826-7480
On Feb 2, 2012, at 4:18 PM, Mark Wiebe wrote:
> On Wed, Feb 1, 2012 at 7:13 PM, Travis Oliphant wrote:
> Hey Mark,
>
> I spent some quality time with your iterator docs tonight and look forwar
On Wed, Feb 1, 2012 at 12:53 PM, Charles R Harris wrote:
> Hi All,
>
> Two things here.
>
> 1) Some macros for threading and the iterator now require a trailing
> semicolon. This change will be reverted before the 1.7 release so that
> scipy 0.10 will compile, but because it is desirable in the l
On Wed, Feb 1, 2012 at 7:13 PM, Travis Oliphant wrote:
> Hey Mark,
>
> I spent some quality time with your iterator docs tonight and look forward
> to getting into the code a bit more soon. I wanted to get your general
> impressions about what it would take to extend the iterator API to handle
On Feb 2, 2012, at 12:58 PM, Ralf Gommers wrote:
>
>
> On Thu, Feb 2, 2012 at 6:36 PM, Charles R Harris
> wrote:
>
>
> On Thu, Feb 2, 2012 at 9:58 AM, Bruce Southey wrote:
> On 02/01/2012 02:53 PM, Charles R Harris wrote:
>>
>> Hi All,
>>
>> Two things here.
>>
>> 1) Some macros for thr
On Thu, Feb 2, 2012 at 6:36 PM, Charles R Harris
wrote:
>
>
> On Thu, Feb 2, 2012 at 9:58 AM, Bruce Southey wrote:
>
>> On 02/01/2012 02:53 PM, Charles R Harris wrote:
>>
>> Hi All,
>>
>> Two things here.
>>
>> 1) Some macros for threading and the iterator now require a trailing
>> semicolon. Th
On Thu, Feb 2, 2012 at 9:58 AM, Bruce Southey wrote:
> On 02/01/2012 02:53 PM, Charles R Harris wrote:
>
> Hi All,
>
> Two things here.
>
> 1) Some macros for threading and the iterator now require a trailing
> semicolon. This change will be reverted before the 1.7 release so that
> scipy 0.10 w
On 02/01/2012 02:53 PM, Charles R Harris wrote:
Hi All,
Two things here.
1) Some macros for threading and the iterator now require a trailing
semicolon. This change will be reverted before the 1.7 release so that
scipy 0.10 will compile, but because it is desirable in the long term
it would
On 02/02/2012 02:52 AM, martin großhauser wrote:
> On Wed, Feb 1, 2012 at 10:57 PM, Pierre Haessig
> wrote:
>> I've no idea what's going on, but here is my $0.02 contribution. I
>> reproduced the bug (numpy 1.5.1) with a rather minimal script. See attached.
> I reproduced the issue with Pierre's
Sorry but I don't understand your last question. Better / more efficient
than what?
-=- Olivier
Le 2 février 2012 07:14, Ruby Stevenson a écrit :
> Exactly, histogram of Z, which itself is an array, for each (x, y).
>
> sorry for getting everyone including myself confused :-)
>
> I think I am n
Exactly, histogram of Z, which itself is an array, for each (x, y).
sorry for getting everyone including myself confused :-)
I think I am now using histogram call correctly ... but I now have a
slightly different question. It maybe better to ask in a different
subject, but here it is any way:
su
On 31/01/2012 18:23, Chris Barker wrote:
On Tue, Jan 31, 2012 at 6:14 AM, Malcolm Reynolds
wrote:
Not exactly an answer to your question, but I can highly recommend
using Boost.python, PyUblas and Ublas for your C++ vectors and
matrices. It gives you a really good interface on the C++ side to
On Wed, Feb 1, 2012 at 10:57 PM, Pierre Haessig
wrote:
> I've no idea what's going on, but here is my $0.02 contribution. I
> reproduced the bug (numpy 1.5.1) with a rather minimal script. See attached.
I reproduced the issue with Pierre's script also in numpy 1.6.1 and
latest github (2.0.0.dev-b
12 matches
Mail list logo
