On Sun, Oct 16, 2011 at 11:02 AM, Tony Yu wrote:
> On Sun, Oct 16, 2011 at 12:49 PM, Pauli Virtanen wrote:
>
>> (16.10.2011 18:39), Tony Yu wrote:
>> > >>> import numpy as np
>> > >>> a = np.arange(10)
>> > >>> b = np.ones(10, dtype=np.uint8)
>> >
>> > # this runs without error
>> > >>> b[:5
On Sun, Oct 16, 2011 at 6:13 PM, Nathaniel Smith wrote:
> On Sun, Oct 16, 2011 at 4:29 PM, Charles R Harris
> wrote:
> > On Sun, Oct 16, 2011 at 4:16 PM, Nathaniel Smith wrote:
> >> I understand the argument that you don't want to call it "float80"
> >> because not all machines support a float8
On Sun, Oct 16, 2011 at 4:29 PM, Charles R Harris
wrote:
> On Sun, Oct 16, 2011 at 4:16 PM, Nathaniel Smith wrote:
>> I understand the argument that you don't want to call it "float80"
>> because not all machines support a float80 type. But I don't
>> understand why we would solve that problem by
On Sun, Oct 16, 2011 at 4:16 PM, Nathaniel Smith wrote:
> On Sun, Oct 16, 2011 at 3:04 PM, Matthew Brett
> wrote:
> > If we agree that float128 is a bad name for something that isn't IEEE
> > binary128, and there is already a longdouble type (thanks for pointing
> > that out), then what about:
>
On Sun, Oct 16, 2011 at 3:04 PM, Matthew Brett wrote:
> If we agree that float128 is a bad name for something that isn't IEEE
> binary128, and there is already a longdouble type (thanks for pointing
> that out), then what about:
>
> Deprecating float128 / float96 as names
> Preferring longdouble f
Hi,
On Sun, Oct 16, 2011 at 2:11 PM, David Cournapeau wrote:
> On Sun, Oct 16, 2011 at 7:40 PM, Matthew Brett
> wrote:
>> Hi,
>
>> If we use float64 we know what that is. If we are using float128,
>> we've got no idea what it is.
>
> I think there is no arguing here: the ideal solution would b
On Sun, Oct 16, 2011 at 7:40 PM, Matthew Brett wrote:
> Hi,
> If we use float64 we know what that is. If we are using float128,
> we've got no idea what it is.
I think there is no arguing here: the ideal solution would be to
follow what happens with 32 and 64 bits reprensentations. But this is
Hi,
On Sun, Oct 16, 2011 at 11:40 AM, Matthew Brett wrote:
> Hi,
>
> On Sun, Oct 16, 2011 at 1:18 AM, David Cournapeau wrote:
>> On Sun, Oct 16, 2011 at 8:33 AM, Matthew Brett
>> wrote:
>>> Hi,
>>>
>>> On Sun, Oct 16, 2011 at 12:28 AM, David Cournapeau
>>> wrote:
On Sun, Oct 16, 2011 at
Hi,
On Sun, Oct 16, 2011 at 1:18 AM, David Cournapeau wrote:
> On Sun, Oct 16, 2011 at 8:33 AM, Matthew Brett
> wrote:
>> Hi,
>>
>> On Sun, Oct 16, 2011 at 12:28 AM, David Cournapeau
>> wrote:
>>> On Sun, Oct 16, 2011 at 8:04 AM, Matthew Brett
>>> wrote:
Hi,
On Sat, Oct 15, 2
I see it now. Thanks!
Alan
>>Couldn't someone add to the page an icon, >> or even a static link, that
>>links to the "action=info" URL?
>> Who's the right person to ask? >It's already there --- it's as part of
>> standard Moinmoin wiki
>configuration --- the one with the letter 'i' in it on th
On Sun, Oct 16, 2011 at 12:49 PM, Pauli Virtanen wrote:
> (16.10.2011 18:39), Tony Yu wrote:
> > >>> import numpy as np
> > >>> a = np.arange(10)
> > >>> b = np.ones(10, dtype=np.uint8)
> >
> > # this runs without error
> > >>> b[:5] = a[:5]
> >
> > >>> mask = a < 5
> > >>> b[mask] = b[mask
(16.10.2011 18:39), Tony Yu wrote:
> >>> import numpy as np
> >>> a = np.arange(10)
> >>> b = np.ones(10, dtype=np.uint8)
>
> # this runs without error
> >>> b[:5] = a[:5]
>
> >>> mask = a < 5
> >>> b[mask] = b[mask]
> TypeError: array cannot be safely cast to required type
Seems to be fixed
On Sun, Oct 16, 2011 at 12:39 PM, Tony Yu wrote:
> Hi,
>
> I noticed a type-checking inconsistency between assignments using slicing
> and fancy-indexing. The first will happily cast on assignment (regardless of
> type), while the second will throw a type error if there's reason to believe
> the
Hi,
I noticed a type-checking inconsistency between assignments using slicing
and fancy-indexing. The first will happily cast on assignment (regardless of
type), while the second will throw a type error if there's reason to believe
the casting will be unsafe. I'm not sure which would be the "corre
(16.10.2011 14:25), Alan Frankel wrote:
[clip]
> Couldn't someone add to the page an icon,
> or even a static link, that links to the "action=info" URL?
> Who's the right person to ask?
It's already there --- it's as part of standard Moinmoin wiki
configuration --- the one with the letter 'i' i
Looks like my change went through after all, despite the internal server error
message.
Alan
- Original Message -
From: Alan Frankel
To: Discussion of Numerical Python
Cc:
Sent: Sunday, October 16, 2011 8:25 AM
Subject: Re: [Numpy-discussion] NumPy example list is corrupted
Thanks
Thanks a lot, Robert. That should enable me to do what I want to do.
Unfortunately, I now get internal server errors whenever I try to commit a
change. The message instructs me to send an e-mail to r...@enthought.com, which
I'll do separately.
Couldn't someone add to the page an icon, or even a
On Sun, Oct 16, 2011 at 01:59, Alan Frankel wrote:
> I've been editing the "Tentative NumPy? Tutorial" and occasionally referring
> to the "NumPy? Example List" ( http://www.scipy.org/Numpy_Example_List ). In
> the process, I think I mistakenly corrupted the NumPy Example List. Since the
> webs
On Sun, Oct 16, 2011 at 8:33 AM, Matthew Brett wrote:
> Hi,
>
> On Sun, Oct 16, 2011 at 12:28 AM, David Cournapeau wrote:
>> On Sun, Oct 16, 2011 at 8:04 AM, Matthew Brett
>> wrote:
>>> Hi,
>>>
>>> On Sat, Oct 15, 2011 at 11:04 PM, Nadav Horesh
>>> wrote:
On 32 bit systems it consumes 96
Hi,
On Sun, Oct 16, 2011 at 12:28 AM, David Cournapeau wrote:
> On Sun, Oct 16, 2011 at 8:04 AM, Matthew Brett
> wrote:
>> Hi,
>>
>> On Sat, Oct 15, 2011 at 11:04 PM, Nadav Horesh
>> wrote:
>>> On 32 bit systems it consumes 96 bits (3 x 32). and hence float96
>>> On 64 bit machines it consume
On Sun, Oct 16, 2011 at 8:04 AM, Matthew Brett wrote:
> Hi,
>
> On Sat, Oct 15, 2011 at 11:04 PM, Nadav Horesh wrote:
>> On 32 bit systems it consumes 96 bits (3 x 32). and hence float96
>> On 64 bit machines it consumes 128 bits (2x64).
>> The variable size is set for an efficient addressing, wh
Hi,
On Sat, Oct 15, 2011 at 11:04 PM, Nadav Horesh wrote:
> On 32 bit systems it consumes 96 bits (3 x 32). and hence float96
> On 64 bit machines it consumes 128 bits (2x64).
> The variable size is set for an efficient addressing, while the calculation
> in hardware is carried in the 80 bits FP
22 matches
Mail list logo
