On Fri, May 6, 2011 at 12:12 AM, Derek Homeier <
de...@astro.physik.uni-goettingen.de> wrote:
>
> On 5 May 2011, at 22:53, Derek Homeier wrote:
>
> >>
> >> However, the problem that ndmin is supposed to address is not fixed
> >> by the current implementation for the rc. Essentially, a single-
> >
Probably just another standard "your BLAS is compiled wrong!" bug, but
in this case I'm seeing it with the stock versions of ATLAS, numpy,
etc. included in the latest Ubuntu release (11.04 Natty Narwhal):
https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/778217
So I thought people might like
On Thu, May 5, 2011 at 11:51 PM, DJ Luscher wrote:
>
> Ralf Gommers googlemail.com> writes:
>
> >
> > Hi,
> >
> > I am pleased to announce the availability of the second release
> > candidate of NumPy 1.6.0.
> >
> > Compared to the first release candidate, one segfault on (32-bit
> > Windows + M
On 5 May 2011, at 22:53, Derek Homeier wrote:
>>
>> However, the problem that ndmin is supposed to address is not fixed
>> by the current implementation for the rc. Essentially, a single-
>> row, multi-column file with ndmin=2 comes out as a Nx1 array which
>> is the same result for a multi-row,
Ralf Gommers googlemail.com> writes:
>
> Hi,
>
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
>
> Compared to the first release candidate, one segfault on (32-bit
> Windows + MSVC) and several memory leaks were fixed. If no new
> problems are rep
On 5 May 2011, at 22:31, Ralf Gommers wrote:
>
> On Thu, May 5, 2011 at 9:46 PM, Benjamin Root wrote:
>
>
> On Thu, May 5, 2011 at 2:33 PM, Ralf Gommers > wrote:
>
>
> On Thu, May 5, 2011 at 9:18 PM, Benjamin Root wrote:
>
>
> On Thu, May 5, 2011 at 1:08 PM, Paul Anton Letnes
> > wrote:
>
> O
On Thu, May 5, 2011 at 9:46 PM, Benjamin Root wrote:
>
>
> On Thu, May 5, 2011 at 2:33 PM, Ralf Gommers
> wrote:
>
>>
>>
>> On Thu, May 5, 2011 at 9:18 PM, Benjamin Root wrote:
>>
>>>
>>>
>>> On Thu, May 5, 2011 at 1:08 PM, Paul Anton Letnes <
>>> paul.anton.let...@gmail.com> wrote:
>>>
>>
On Thu, May 5, 2011 at 2:33 PM, Ralf Gommers wrote:
>
>
> On Thu, May 5, 2011 at 9:18 PM, Benjamin Root wrote:
>
>>
>>
>> On Thu, May 5, 2011 at 1:08 PM, Paul Anton Letnes <
>> paul.anton.let...@gmail.com> wrote:
>>
>>>
>>> On 5. mai 2011, at 08.49, Benjamin Root wrote:
>>>
>>> >
>>> >
>>> > On W
On Thu, May 5, 2011 at 9:18 PM, Benjamin Root wrote:
>
>
> On Thu, May 5, 2011 at 1:08 PM, Paul Anton Letnes <
> paul.anton.let...@gmail.com> wrote:
>
>>
>> On 5. mai 2011, at 08.49, Benjamin Root wrote:
>>
>> >
>> >
>> > On Wed, May 4, 2011 at 11:08 PM, Paul Anton Letnes <
>> paul.anton.let...@g
On Thu, May 5, 2011 at 1:08 PM, Paul Anton Letnes <
paul.anton.let...@gmail.com> wrote:
>
> On 5. mai 2011, at 08.49, Benjamin Root wrote:
>
> >
> >
> > On Wed, May 4, 2011 at 11:08 PM, Paul Anton Letnes <
> paul.anton.let...@gmail.com> wrote:
> >
> > On 4. mai 2011, at 20.33, Benjamin Root wrote:
On Thu, May 5, 2011 at 1:10 AM, Benjamin Root wrote:
>
>
> On Tue, May 3, 2011 at 1:18 PM, Ralf Gommers
> wrote:
>
>> Hi,
>>
>> I am pleased to announce the availability of the second release
>> candidate of NumPy 1.6.0.
>>
>> Compared to the first release candidate, one segfault on (32-bit
>> W
On 5. mai 2011, at 08.49, Benjamin Root wrote:
>
>
> On Wed, May 4, 2011 at 11:08 PM, Paul Anton Letnes
> wrote:
>
> On 4. mai 2011, at 20.33, Benjamin Root wrote:
>
> > On Wed, May 4, 2011 at 7:54 PM, Derek Homeier
> > wrote:
> > On 05.05.2011, at 2:40AM, Paul Anton Letnes wrote:
> >
> >
On Thu, May 5, 2011 at 9:54 AM, Robert Kern wrote:
> On Thu, May 5, 2011 at 02:29, Christoph Groth wrote:
>> Has something like __index_iadd__ ever been considered seriously? Not
>> to my (limited) knowledge.
>
> Only on this list, I think. :-)
>
> I don't think it will ever happen. Only numpy r
On Thu, May 5, 2011 at 02:29, Christoph Groth wrote:
>> On Wed, May 4, 2011 at 6:19 AM, Christoph Groth wrote:
>>>
>>> Dear numpy experts,
>>>
>>> I have noticed that with Numpy 1.5.1 the operation
>>>
>>> m[::2] += 1.0
>>>
>>> takes twice as long as
>>>
>>> t = m[::2]
>>>
On Thu, May 5, 2011 at 10:49 AM, Benjamin Root wrote:
>
>
> On Wed, May 4, 2011 at 11:08 PM, Paul Anton Letnes <
> paul.anton.let...@gmail.com> wrote:
>
>>
>> On 4. mai 2011, at 20.33, Benjamin Root wrote:
>>
>> > On Wed, May 4, 2011 at 7:54 PM, Derek Homeier <
>> de...@astro.physik.uni-goettinge
On Wed, May 4, 2011 at 11:08 PM, Paul Anton Letnes <
paul.anton.let...@gmail.com> wrote:
>
> On 4. mai 2011, at 20.33, Benjamin Root wrote:
>
> > On Wed, May 4, 2011 at 7:54 PM, Derek Homeier <
> de...@astro.physik.uni-goettingen.de> wrote:
> > On 05.05.2011, at 2:40AM, Paul Anton Letnes wrote:
>
On Wed, May 04, 2011 at 08:57:42AM -0700, Mark Wiebe wrote:
>You'd better time this in 1.6 too. ;)
>
> [2]https://github.com/numpy/numpy/commit/f60797ba64ccf33597225d23b893b6eb11149860
Awesome work! That's all I have to say.
I find very enjoyable the generalized use of the time machine i
> On Wed, May 4, 2011 at 6:19 AM, Christoph Groth wrote:
>>
>> Dear numpy experts,
>>
>> I have noticed that with Numpy 1.5.1 the operation
>>
>> m[::2] += 1.0
>>
>> takes twice as long as
>>
>> t = m[::2]
>> t += 1.0
Mark Wiebe writes:
> You'd better tim
18 matches
Mail list logo
