[Numpy-discussion] Problems with long

Hi, I'm having some troubles with long. >>> from numpy import log >>> log(8463186938969424928L) 43.5822574833 >>> log(10454852688145851272L) : 'long' object has no attribute 'log' Thoughts? ___ Numpy-discussion mailing list Numpy-discussion@scipy.org ht

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Charles R Harris wrote: > > > On Jan 25, 2008 3:21 AM, David Cournapeau > <[EMAIL PROTECTED] > > wrote: > > Matthew Brett wrote: > > Hi David, > > > >>> Basically, I'm trying to understand the library discovery, linking > >>> steps - ATLAS in particul

[Numpy-discussion] tensordot bug?

Is this a bug? In [21]: a = ones((2,2)) In [22]: b = ones((2,2,2,2)) In [23]: tensordot(a, tensordot(b, a, 2), 2) Out[23]: array(16.0) It seems to me that consistency with the dot product would require a scalar result, not a 0-dim array. Also, do we have a plain old tensor product? Outer flatt

Re: [Numpy-discussion] NPY_FORCECAST

Bill Spotz wrote: > Hi, > > I am currently using PyArray_FromObject() to convert an input > argument to a 32-bit integer array. On a 64-bit architecture, it is > easy to create an integer array whose default type is 64-bit. When > this is sent to PyArray_FromObject(), it raises an error, sa

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

On Jan 25, 2008 3:21 AM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Matthew Brett wrote: > > Hi David, > > > >>> Basically, I'm trying to understand the library discovery, linking > >>> steps - ATLAS in particular. > >> Don't trust the included doc: it is not up-to-date, and that's the part > >

Re: [Numpy-discussion] extending a recarray

Kevin Christman wrote: > I am using recarray to store experiment information that is read from a file: > > self.records = > numpy.rec.fromrecords(self.allData,formats='f4,S30,S30,f4,f4,f4,f4,f4,f4,f4,f4,f4,f4',names='MotorNum,MotorType,MotorName,MotorHP, > NSync,NShaftFL,NShaft,pLoad,pLoadSlipMe

[Numpy-discussion] extending a recarray

I am using recarray to store experiment information that is read from a file: self.records = numpy.rec.fromrecords(self.allData,formats='f4,S30,S30,f4,f4,f4,f4,f4,f4,f4,f4,f4,f4',names='MotorNum,MotorType,MotorName,MotorHP, NSync,NShaftFL,NShaft,pLoad,pLoadSlipMethod, pLoadORMEL,etaMeasured,eta

[Numpy-discussion] NPY_FORCECAST

Hi, I am currently using PyArray_FromObject() to convert an input argument to a 32-bit integer array. On a 64-bit architecture, it is easy to create an integer array whose default type is 64-bit. When this is sent to PyArray_FromObject(), it raises an error, saying "array cannot be safel

[Numpy-discussion] Doc-days are today! Come join on irc.freenode.net (#scipy)

___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Neal Becker wrote: > Is numscons specific to numpy/scipy, or is it for building arbitrary python > extensions (replacing distutils?). I'm hoping for the latter. Actually, another way to answer your question: I am working on a patch such as the part of numscons which takes care of building python

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Is numscons specific to numpy/scipy, or is it for building arbitrary python extensions (replacing distutils?). I'm hoping for the latter. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discu

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Hi, > > I've attached the build logs. I noticed that, for atlas, you check > > for atlas_enum.c - but do you in fact need this for the build? > Now. I just wanted one header specific to atlas. It looks like not all > version of ATLAS install this one, unfortunately (3.8, for example). > > numpy.d

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Matthew Brett wrote: > Hi David, > >>> Basically, I'm trying to understand the library discovery, linking >>> steps - ATLAS in particular. >> Don't trust the included doc: it is not up-to-date, and that's the part >> which I totally redesigned since I wrote the initial doc. > >> - For a perflib

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Hi David, > > Basically, I'm trying to understand the library discovery, linking > > steps - ATLAS in particular. > Don't trust the included doc: it is not up-to-date, and that's the part > which I totally redesigned since I wrote the initial doc. > - For a perflib check to succeed, I try to

[Numpy-discussion] numscons, available as python egg

Hi, Sorry for the flooding, but I finally managed to build an egg and put it on the web, so numscons is available as an egg, now. You should be able to install it using easy_install, e.g easy_install numscons should work. cheers, David ___ Nump

Re: [Numpy-discussion] How to build on Solaris 10 (x86) using sunperf?

On Jan 24, 2008 3:06 AM, Peter Ward <[EMAIL PROTECTED]> wrote: > > The problems I was having were due to a bad site.cfg initially and then > a problem with the python pkg from sunfreeware (ctypes version > mismatch). > > Numpy is now happily installed. > > If you need someone to test anything new,

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

dmitrey wrote: > Hi all, > I don't know much about what are these scons are, if it's something > essential (as it seems to be from amount of mailing list traffic) why > can't it be just merged to numpy, w/o making any additional branches? scons is a build system, like make. The difference being t

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

2008/1/25, dmitrey <[EMAIL PROTECTED]>: > > Hi all, > I don't know much about what are these scons are, if it's something > essential (as it seems to be from amount of mailing list traffic) why > can't it be just merged to numpy, w/o making any additional branches? > Scons is a building system, li

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

dmitrey wrote: > Hi all, > I don't know much about what are these scons are, if it's something > essential (as it seems to be from amount of mailing list traffic) why > can't it be just merged to numpy, w/o making any additional branches? It's a very large, still experimental change to the entir

Re: [Numpy-discussion] [ANN] numscons 0.3.0 release

Hi all, I don't know much about what are these scons are, if it's something essential (as it seems to be from amount of mailing list traffic) why can't it be just merged to numpy, w/o making any additional branches? Regards, D. David Cournapeau wrote: > > _