On Wed, Nov 26, 2008 at 12:59 AM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
>
> Apart from the Mac, the ppc can be configured to run either bigendian or
> littleendian, so the hardware encompasses more than just the cpu, it's the
> whole darn board.
Yep, many CPU families have double endian supp
On Tue, Nov 25, 2008 at 8:03 AM, David Cournapeau <[EMAIL PROTECTED]>wrote:
> On Tue, Nov 25, 2008 at 10:55 PM, David Cournapeau
> <[EMAIL PROTECTED]> wrote:
>
> >
> > I used the path of least resistance: instead of using the
> > WORDS_BIGENDIAN macro, I added a numpy header which gives the endian
On Tue, Nov 25, 2008 at 10:55 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
>
> I used the path of least resistance: instead of using the
> WORDS_BIGENDIAN macro, I added a numpy header which gives the endianness
> every time it is included. IOW, instead of the endianness to be fixed at
> numpy
David Cournapeau wrote:
> Pierre GM wrote:
>
>> FYI,
>> I can't reproduce David's failures on my machine (intel core2 duo w/
>> 10.5.5)
>> * python 2.6 from macports
>>
>>
>
> I think that's the main difference. I feel more and more that the
> problem is linked to fat binaries (more ex
Pierre GM wrote:
> FYI,
> I can't reproduce David's failures on my machine (intel core2 duo w/
> 10.5.5)
> * python 2.6 from macports
>
I think that's the main difference. I feel more and more that the
problem is linked to fat binaries (more exactly multi arch build in one
autoconf run: since
FYI,
I can't reproduce David's failures on my machine (intel core2 duo w/
10.5.5)
* python 2.6 from macports
* numpy svn 6098
* GCC 4.0.1 (Apple Inc. build 5488)
I have only 1 failure:
FAIL: test_umath.TestComplexFunctions.test_against_cmath
--
On Mon, 2008-11-24 at 22:06 -0700, Charles R Harris wrote:
>
>
> Well, it may not be that easy to figure. The (generated)
> pyconfig-32.h has
>
> /* Define to 1 if your processor stores words with the most
> significant byte
> first (like Motorola and SPARC, unlike Intel and VAX).
On Mon, 2008-11-24 at 21:38 -0700, Charles R Harris wrote:
>
>
> On Mon, Nov 24, 2008 at 9:02 PM, David Cournapeau <[EMAIL PROTECTED]>
> wrote:
> On Tue, Nov 25, 2008 at 12:41 PM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> >
>
> > 1) This problem is s
On Mon, Nov 24, 2008 at 9:58 PM, Charles R Harris <[EMAIL PROTECTED]
> wrote:
>
>
> On Mon, Nov 24, 2008 at 9:38 PM, Charles R Harris <
> [EMAIL PROTECTED]> wrote:
>
>>
>>
>> On Mon, Nov 24, 2008 at 9:02 PM, David Cournapeau <[EMAIL PROTECTED]>wrote:
>>
>>> On Tue, Nov 25, 2008 at 12:41 PM, Charle
On Mon, Nov 24, 2008 at 9:38 PM, Charles R Harris <[EMAIL PROTECTED]
> wrote:
>
>
> On Mon, Nov 24, 2008 at 9:02 PM, David Cournapeau <[EMAIL PROTECTED]>wrote:
>
>> On Tue, Nov 25, 2008 at 12:41 PM, Charles R Harris
>> <[EMAIL PROTECTED]> wrote:
>> >
>>
>> > 1) This problem is specific to 2.6 and
On Mon, Nov 24, 2008 at 9:02 PM, David Cournapeau <[EMAIL PROTECTED]>wrote:
> On Tue, Nov 25, 2008 at 12:41 PM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> >
>
> > 1) This problem is specific to 2.6 and 2.5 works.
>
> Yes
>
> > 2) It's on Intel hardware?
>
> Yes.
>
> Here is a minimal test whi
On Tue, Nov 25, 2008 at 12:41 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
>
> 1) This problem is specific to 2.6 and 2.5 works.
Yes
> 2) It's on Intel hardware?
Yes.
Here is a minimal test which shows the problem:
import numpy as np
assert np.dtype('http://projects.scipy.org/mailman/listi
On Mon, Nov 24, 2008 at 8:18 PM, David Cournapeau <[EMAIL PROTECTED]>wrote:
> Hi,
>
> Following the discussion on python 2.6 support for numpy, I tried last
> svn on mac os X, and I get a number of failures which I don't
> understand, which seem to be linked to dtype code, more exactly to
> endian
Hi,
Following the discussion on python 2.6 support for numpy, I tried last
svn on mac os X, and I get a number of failures which I don't
understand, which seem to be linked to dtype code, more exactly to
endianness:
==
FAIL: tes
14 matches
Mail list logo
