Hi,
* Ralf Gommers [2012-07-19]:
> On Thu, Jul 19, 2012 at 4:14 PM, Charles R Harris > On Thu, Jul 19, 2012 at 7:45 AM, Travis Oliphant wrote:
> >
> >> I'm not sure what the conclusion actually was from this long thread.
> >>
> >> But, in trying to update the 1.7.x branch, I ended up in a very o
On Jul 19, 2012, at 9:14 AM, Charles R Harris wrote:
>
>
> On Thu, Jul 19, 2012 at 7:45 AM, Travis Oliphant wrote:
> I'm not sure what the conclusion actually was from this long thread.
>
> But, in trying to update the 1.7.x branch, I ended up in a very odd state
> with respect to the githu
On Tue, Jul 17, 2012 at 6:34 AM, David Goldsmith wrote:
> Hi, folks! Having a problem w/ the Windows installer; first, the
> "back-story": I have both Python 2.7 and 3.2 installed. When I run the
> installer and click next on the first dialog, I get the message that I need
> Python 2.7, which wa
Hi,
I am pleased to announce the availability of the first release candidate of
SciPy 0.11.0. For this release many new features have been added, and over
120 tickets and pull requests have been closed. Also noteworthy is that the
number of contributors for this release has risen to over 50. Some
On Thu, Jul 19, 2012 at 5:58 PM, Ondřej Čertík wrote:
> On Thu, Jul 19, 2012 at 12:58 PM, Ondřej Čertík
> wrote:
> >>> I've nailed it to:
> >>>
> >> import numpy as np
> >> np.array([complex(0, 1)], np.complex64)
> >>> wine: Unhandled page fault on read access to 0x at address
> >
On Thu, Jul 19, 2012 at 12:58 PM, Ondřej Čertík wrote:
>>> I've nailed it to:
>>>
>> import numpy as np
>> np.array([complex(0, 1)], np.complex64)
>>> wine: Unhandled page fault on read access to 0x at address
>>> (nil) (thread 0009), starting debugger...
>>> ...
>
> Btw, I tried t
On Thu, Jul 19, 2012 at 4:14 PM, Charles R Harris wrote:
>
>
> On Thu, Jul 19, 2012 at 7:45 AM, Travis Oliphant wrote:
>
>> I'm not sure what the conclusion actually was from this long thread.
>>
>> But, in trying to update the 1.7.x branch, I ended up in a very odd state
>> with respect to the g
On Thu, Jul 19, 2012 at 7:45 AM, Travis Oliphant wrote:
> I'm not sure what the conclusion actually was from this long thread.
>
> But, in trying to update the 1.7.x branch, I ended up in a very odd state
> with respect to the github pages. I used git filter-branch to try and get
> rid of "empty
On Jul 19, 2012, at 3:50 AM, Nathaniel Smith wrote:
> So the underlying problem with the controversial inplace_increment
> PR[1] is that currently, there's actually nothing in the public numpy
> API that exposes the workings of numpy indexing. The only thing you
> can do with a numpy index is cal
On Jul 19, 2012, at 4:56 AM, Nathaniel Smith wrote:
> On Thu, Jul 19, 2012 at 6:04 AM, Frédéric Bastien wrote:
>> On Tue, Jul 17, 2012 at 10:20 PM, Travis Oliphant
>> wrote:
>>> I will hold off on this one, but only because you raised your objection to
>>> -1 (instead of -0.5).But, I disa
I'm not sure what the conclusion actually was from this long thread.
But, in trying to update the 1.7.x branch, I ended up in a very odd state with
respect to the github pages. I used git filter-branch to try and get rid of
"empty" commits that were showing up for some reason. However, this
>> I've nailed it to:
>>
> import numpy as np
> np.array([complex(0, 1)], np.complex64)
>> wine: Unhandled page fault on read access to 0x at address
>> (nil) (thread 0009), starting debugger...
>> ...
Btw, I tried to debug it using:
$ winedbg --gdb "C:\Python27\python"
and I got
Hi All,
I have spot a strange behavior of numpy.fromfunction(). The sample codes are
as follows:
>>> import numpy as np
>>> def myOnes(i,j):
return 1.0
>>> a = np.fromfunction(myOnes,(2000,2000))
>>> a
1.0
Actually what I expected is that the function will return a 20
On Thu, Jul 19, 2012 at 2:24 AM, Ondřej Čertík wrote:
> Hi Ralf,
>
> On Wed, Jul 18, 2012 at 7:25 PM, Ralf Gommers
> wrote:
>>
>>
>> On Wed, Jul 18, 2012 at 1:24 PM, Ondřej Čertík
>> wrote:
>>>
>>> Hi,
>>>
>>> I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and
>>> here is a full
On Thu, Jul 19, 2012 at 8:56 AM, Ralf Gommers
wrote:
>
>
> On Thu, Jul 12, 2012 at 1:54 PM, Nathaniel Smith wrote:
>>
>> On Thu, Jul 12, 2012 at 12:48 PM, Benjamin Root wrote:
>> >
>> >
>> > On Thursday, July 12, 2012, Thouis (Ray) Jones wrote:
>> >>
>> >> On Thu, Jul 12, 2012 at 1:28 AM, Charle
On Thu, Jul 19, 2012 at 6:04 AM, Frédéric Bastien wrote:
> On Tue, Jul 17, 2012 at 10:20 PM, Travis Oliphant wrote:
>> I will hold off on this one, but only because you raised your objection to
>> -1 (instead of -0.5).But, I disagree very strongly with you that it is
>> "sub-optimal" in the
So the underlying problem with the controversial inplace_increment
PR[1] is that currently, there's actually nothing in the public numpy
API that exposes the workings of numpy indexing. The only thing you
can do with a numpy index is call ndarray.__getattr__ or __setattr__.
This is a pretty obvious
17 matches
Mail list logo
