On Tue, Mar 24, 2009 at 6:32 AM, Bruce Southey wrote:
> I get a problem with using longdouble as that is the dtype that causes
> the TestPower.test_large_types to crash.
Hey, when I said the windows 64 bits support was experimental, I meant it :)
> Also, np.finfo(np.float128) crashes. I can as
2009/3/24 Charles R Harris :
>
>
> On Mon, Mar 23, 2009 at 12:34 PM, Robert Pyle
> wrote:
>>
>> Hi all,
>>
>> This is a continuation of something I started last week, but with a
>> more appropriate subject line.
>>
>> To recap, my machine is a dual G5 running OS X 10.5.6, my python is
>>
>> Pyt
On Mon, Mar 23, 2009 at 6:06 PM, Pauli Virtanen wrote:
> Mon, 23 Mar 2009 16:52:28 -0600, Charles R Harris wrote:
> [clip]
> >> > >>> y=np.longdouble(2)
> >> > >>> y
> >> > 2.0
> >> > >>> y**1
> >> > 2.0
> >> > >>> y**2
> >> > crash
> >>
> >> Ok, this looks a bit tricky, I have no idea what's
Mon, 23 Mar 2009 16:52:28 -0600, Charles R Harris wrote:
[clip]
>> > >>> y=np.longdouble(2)
>> > >>> y
>> > 2.0
>> > >>> y**1
>> > 2.0
>> > >>> y**2
>> > crash
>>
>> Ok, this looks a bit tricky, I have no idea what's going on. Why does
>> it not crash with the exponent 1...
>
> I'd guess becaus
On Mon, Mar 23, 2009 at 4:27 PM, Pauli Virtanen wrote:
> Mon, 23 Mar 2009 16:32:47 -0500, Bruce Southey wrote:
> [clip: crashes with longdouble on Windows 64]
> > No.
> >
> > I get a problem with using longdouble as that is the dtype that causes
> > the TestPower.test_large_types to crash. Also,
Mon, 23 Mar 2009 16:18:52 -0600, Charles R Harris wrote:
[clip: #1008 fixes]
>> Backport?
>>
>>
> I think so. It is a bug and the fix doesn't look complicated.
>
> I don't much like all the ifdefs in the middle of the code, but if there
> is a cleaner way to do it, it can wait.
Done, r6717.
Sorr
Mon, 23 Mar 2009 16:32:47 -0500, Bruce Southey wrote:
[clip: crashes with longdouble on Windows 64]
> No.
>
> I get a problem with using longdouble as that is the dtype that causes
> the TestPower.test_large_types to crash. Also, np.finfo(np.float128)
> crashes. I can assign and multiple longdoub
On Mon, Mar 23, 2009 at 4:01 PM, Pauli Virtanen wrote:
> Mon, 23 Mar 2009 19:55:17 +, Pauli Virtanen wrote:
>
> > Mon, 23 Mar 2009 13:22:29 -0600, Charles R Harris wrote: [clip]
> >> PPC stores long doubles as two doubles. I don't recall exactly how the
> >> two are used, but the result is th
Mon, 23 Mar 2009 19:55:17 +, Pauli Virtanen wrote:
> Mon, 23 Mar 2009 13:22:29 -0600, Charles R Harris wrote: [clip]
>> PPC stores long doubles as two doubles. I don't recall exactly how the
>> two are used, but the result is that the numbers aren't in the form you
>> would expect. Long double
On Mon, Mar 23, 2009 at 3:57 PM, Charles R Harris wrote:
>
>
> On Mon, Mar 23, 2009 at 3:32 PM, Bruce Southey wrote:
>
>> Pauli Virtanen wrote:
>> > Mon, 23 Mar 2009 15:03:09 -0500, Bruce Southey wrote:
>> > [clip]
>> >
>> >> I do not know if this is related, but I got similar error with David's
On Mon, Mar 23, 2009 at 3:32 PM, Bruce Southey wrote:
> Pauli Virtanen wrote:
> > Mon, 23 Mar 2009 15:03:09 -0500, Bruce Southey wrote:
> > [clip]
> >
> >> I do not know if this is related, but I got similar error with David's
> >> windows 64 bits installer on my 64 bit Vista system.
> >> http://
Pauli Virtanen wrote:
> Mon, 23 Mar 2009 15:03:09 -0500, Bruce Southey wrote:
> [clip]
>
>> I do not know if this is related, but I got similar error with David's
>> windows 64 bits installer on my 64 bit Vista system.
>> http://mail.scipy.org/pipermail/numpy-discussion/2009-March/041282.html
>>
Hello,
I'm pleased to announce that Enthought Tool Suite (ETS) version 3.2.0
has been tagged and released!
Source distributions (.tar.gz) have been uploaded to PyPi, and Windows
binaries will be follow shortly. A full install of ETS can be done using
Setuptools via a command like:
easy_install
On Mon, Mar 23, 2009 at 2:22 PM, Robert Pyle wrote:
> > PPC stores long doubles as two doubles. I don't recall exactly how
> > the two are used, but the result is that the numbers aren't in the
> > form you would expect. Long doubles on the PPC have always been
> > iffy, so it is no surprise that
Sturla Molden wrote:
>> def fromaddress(address, nbytes, dtype=double):
I guess dtype=float works better...
S.M.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
> PPC stores long doubles as two doubles. I don't recall exactly how
> the two are used, but the result is that the numbers aren't in the
> form you would expect. Long doubles on the PPC have always been
> iffy, so it is no surprise that machar fails. The failure on SPARC
> quad precision b
Mon, 23 Mar 2009 15:03:09 -0500, Bruce Southey wrote:
[clip]
> I do not know if this is related, but I got similar error with David's
> windows 64 bits installer on my 64 bit Vista system.
> http://mail.scipy.org/pipermail/numpy-discussion/2009-March/041282.html
>
> In particular this code crashes
On 23/03/09 15:40, Sturla Molden wrote:
> Jens Rantil wrote:
> > Hi all,
> >
> > So I have a C-function in a DLL loaded through ctypes. This particular
> > function returns a pointer to a double. In fact I know that this
> > pointer points to the first element in an array of, say for simplicity,
Pauli Virtanen wrote:
> Mon, 23 Mar 2009 13:22:29 -0600, Charles R Harris wrote:
> [clip]
>
>> PPC stores long doubles as two doubles. I don't recall exactly how the
>> two are used, but the result is that the numbers aren't in the form you
>> would expect. Long doubles on the PPC have always be
Mon, 23 Mar 2009 13:22:29 -0600, Charles R Harris wrote:
[clip]
> PPC stores long doubles as two doubles. I don't recall exactly how the
> two are used, but the result is that the numbers aren't in the form you
> would expect. Long doubles on the PPC have always been iffy, so it is no
> surprise th
On Mon, Mar 23, 2009 at 12:34 PM, Robert Pyle wrote:
> Hi all,
>
> This is a continuation of something I started last week, but with a
> more appropriate subject line.
>
> To recap, my machine is a dual G5 running OS X 10.5.6, my python is
>
>Python 2.5.2 |EPD Py25 4.1.30101| (r252:60911, Dec
Alright, I solved this by using numscons.
On Mon, Mar 23, 2009 at 12:48 AM, charlie wrote:
> Dear numpyers,
>
> I am trying to install numpy 1.3 with my own version of python 2.5. I got
> stuck with following error:
> *building 'numpy.core.multiarray' extension
> compiling C sources
> C compiler
Hi all,
This is a continuation of something I started last week, but with a
more appropriate subject line.
To recap, my machine is a dual G5 running OS X 10.5.6, my python is
Python 2.5.2 |EPD Py25 4.1.30101| (r252:60911, Dec 19 2008,
15:28:32)
and numpy 1.3.0b1 was installed from the s
Jens Rantil wrote:
> Hi all,
>
> So I have a C-function in a DLL loaded through ctypes. This particular
> function returns a pointer to a double. In fact I know that this
> pointer points to the first element in an array of, say for simplicity,
> 200 elements.
>
> How do I convert this pointer t
Hi all,
So I have a C-function in a DLL loaded through ctypes. This particular
function returns a pointer to a double. In fact I know that this
pointer points to the first element in an array of, say for simplicity,
200 elements.
How do I convert this pointer to a NumPy array that uses this da
How did you import the function? f2py? What did you put in your .pyf file?
> *My Fortran code:*
>
> subroutine print_string (a, c)
> implicit none
> character(len=255), dimension(c), intent(inout):: a
> integer, intent(in) :: c
> integer :: i
> do i = 1, size(a)
> print*, a(i)
> end do
>
> end
A Saturday 21 March 2009, Paul Northug escrigué:
[clip]
> numpy arrays are not hashable, maybe for a good reason.
Numpy array are not hashable because they are mutable.
> I tried
> anyway by keeping a dict of hash(tuple(X)), but started having
> collisions. So I switched to md5.new(X).digest()
Dear numpyers,
I am trying to install numpy 1.3 with my own version of python 2.5. I got
stuck with following error:
*building 'numpy.core.multiarray' extension
compiling C sources
C compiler: gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes -fPIC
creating build
Hi Matthew,
On Sun, Mar 22, 2009 at 5:40 PM, Matthew Brett wrote:
>
> I get the 'negative dimensions' error in this situation:
I think I have fixed both arange and zeros errors in the trunk. arange
error was specific to arange (unchecked overflow in a double -> int
cast), but the zero one was mo
29 matches
Mail list logo
