I just tried this on one of our G4's and see the same behavior.
Chris
Original message
>Date: Thu, 26 Oct 2006 15:46:50 +0100
>From: Andrew Jaffe <[EMAIL PROTECTED]>
>Subject: Re: [Numpy-discussion] Still a ticket 112 "check_longfloat_repr"
>issue on OSX
>To: Discussion of Numeric
Greetings,
I can't decide if the following is a bug or feature. Numpy scalars are
allowed to overflow silently while numarray upcasts to a larger python
type. I guess my biggest problem is that the overflow occurs silently.
In any case, is this known and expected behavior?
Thanks,
Chris
N
Hi,
Change set 3213 changed the data type printing with an array from
something like dtype=int64 to dtype='int64'. Although this is a small
cosmetic change it has broken all of the doctests I have written for
numpy code. I expect that I am not the only person this change has
caught. Please
Travis,
Numpy version '1.0b4.dev3060' will now build on both a 32bit Red Hat
Enterprise 3 machine as well as Solaris 8.
Chris
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickl
Good Morning,
Numpy revision 3056 will not build on either Red Hat Enterprise 3 or
Solaris 8. The relevant syntax errors are below:
For RHE3:
-
creating build/temp.linux-i686-2.4
creating build/temp.linux-i686-2.4/numpy
creating build/temp.linux-i686-2.4/numpy/core
creating build/temp.
What happened to numpy.bool8? I realize that bool_ is just as good. I
was just wondering what motivated the change?
Chris
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly w
>>Get the basearray into the python core and
>>for sure I will be using that, whatever it is called. I was tempted to
>>switch to numarray in the past because of the nd_image, but I don't see
>>that in numpy just yet?
>>
>>
>
> It is in SciPy where it belongs (you can also install it as a se
Greetings,
Numpy revision 2680 causes a segfault in the unit tests on the Solaris 8
OS. The unit tests fail with the at the following test:
check_vecobject (numpy.core.tests.test_numeric.test_dot)Segmentation
Fault (core dumped)
I can try and isolate what in the test is failing.
What I can t
>You will also need to change the include directories used in compiling
>by appending the directories returned by
>numpy.numarray.util.get_numarray_include_dirs()
>
Hi Travis,
I believe that there is a problem with this function. When executing
interactively with numpy version 0.9.9.2660 I ge
The last successful run was with revision 2613. However, revision 2624
appears to have corrected the problem on Solaris.
Thanks,
Chris
Travis Oliphant wrote:
> Christopher Hanley wrote:
>
>> The daily numpy build and tests I run have failed for revision 2617.
>> Below is
The daily numpy build and tests I run have failed for revision 2617.
Below is the error message I receive on my RHE 3 box:
==
FAIL: Check reading the nested fields of a nested array (1st level)
---
Robert Kern wrote:
>
> Depends. Do you want the actual bytes to swap, or are you content with
> getting a
> view that pretends the bytes are swapped? If the latter:
I want the actual bytes to swap.
Thanks,
Chris
___
Numpy-discussion mailing list
Num
Hi,
Is there a way to byte swap a ndarray in place? The "byteswap" method I
have found on an ndarray object currently returns a new array.
Example:
In [16]: a = n.array([1,2,3,4,5])
In [17]: a
Out[17]: array([1, 2, 3, 4, 5])
In [18]: b = a.byteswap()
In [19]: b
Out[19]: array([16777216, 335544
13 matches
Mail list logo
