And I forgot to attach the relevant code (though it is also in my fork)...
On Sun, May 13, 2012 at 6:28 PM, Anthony Scopatz wrote:
> Hello All,
>
> This week, while doing some optimization, I found that np.fromstring()
> is significantly slower than many alternatives out there. This function
>
Hello All,
This week, while doing some optimization, I found that np.fromstring()
is significantly slower than many alternatives out there. This function
basically does two things: (1) it splits the string and (2) it converts the
data to the desired type.
There isn't much we can do about the con
Hello. I am new to the list thanks for accepting my question.
I am trying to run the attached code, directly from the book in the title.
It simply calculates correlation of returns of the stock listed in the
spreadsheets. could it be that the numPY library is not being recognized on my
syste
On Sat, May 12, 2012 at 9:50 PM, Ralf Gommers
wrote:
>
>
> On Sun, May 6, 2012 at 12:12 AM, Charles R Harris
> wrote:
>>
>>
>>
>> On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes
>> wrote:
>>>
>>> Hi,
>>>
>>> I'm getting a couple of errors when testing. System:
>>> Arch Linux (updated today)
>>
On Sun, May 13, 2012 at 3:28 AM, Travis Oliphant wrote:
> Another approach would be to introduce a method:
>
> a.diag(copy=False)
>
> and leave a.diagonal() alone. Then, a.diagonal() could be deprecated over
> 2-3 releases.
This would be a good idea if we didn't already have both
np.diagonal(a)
+1
On Sun, May 13, 2012 at 4:28 AM, Travis Oliphant wrote:
> Another approach would be to introduce a method:
>
> a.diag(copy=False)
>
> and leave a.diagonal() alone. Then, a.diagonal() could be deprecated over
> 2-3 releases.
>
> -Travis
>
>
> On May 12, 2012, at 8:31 AM, Ralf Gommers wrote:
>
