Re: [Numpy-discussion] Error while upgrading to numpy 1.4.1

On Mon, Jun 14, 2010 at 3:00 PM, Vishal Rana wrote: > Hi, > I am getting this error while upgrading to numpy 1.4.1 from 1.3 on ubuntu > 10.04 using easy_install -U numpy command, I even tried downloading / > installing numpy 1.4.1 but no luck, help appreciated. First, do not use easy_install to u

[Numpy-discussion] Error while upgrading to numpy 1.4.1

Hi, I am getting this error while upgrading to numpy 1.4.1 from 1.3 on ubuntu 10.04 using easy_install -U numpy command, I even tried downloading / installing numpy 1.4.1 but no luck, help appreciated. /usr/lib/python2.6/dist-packages/setuptools/package_index.py:156: UserWarning: Unbuilt egg for

Re: [Numpy-discussion] Serializing numpy record array

Thanks Robert, it worked. On Sun, Jun 13, 2010 at 6:23 PM, Robert Kern wrote: > On Sun, Jun 13, 2010 at 20:10, Vishal Rana wrote: > > Robert, > > There is no error on python side but on flex client which > > is "Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: > > Status 503"

Re: [Numpy-discussion] numpy for jython

On Sun, Jun 13, 2010 at 20:58, David wrote: > On 06/14/2010 10:23 AM, Jarl Haggerty wrote: >> Does anyone have any interest in a port of numpy to jython? > > I am insterested, and I think interest is growing thanks to the cloud > computing fad, since a lot of this instrastructure is based on java

Re: [Numpy-discussion] numpy for jython

On 06/14/2010 10:23 AM, Jarl Haggerty wrote: > Does anyone have any interest in a port of numpy to jython? I am insterested, and I think interest is growing thanks to the cloud computing fad, since a lot of this instrastructure is based on java (hadoop, hbase, cassandra to name a few). Being abl

[Numpy-discussion] numpy for jython

Does anyone have any interest in a port of numpy to jython? I've been looking around and it seems like the only versions of this is JNumeric, which is so old it's named after Numeric, and a slightly updated version of that. I decided to try and use jnumeric but it's missing a lot of features, the

Re: [Numpy-discussion] Serializing numpy record array

On Sun, Jun 13, 2010 at 20:10, Vishal Rana wrote: > Robert, > There is no error on python side but on flex client which > is "Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: > Status 503" > Here is the documentation for type mapping flex vs > python: http://pyamf.org/architectur

Re: [Numpy-discussion] Serializing numpy record array

Robert, There is no error on python side but on flex client which is "*Channel*.* Call*.*Failed*" faultDetail="NetConnection.Call.Failed: *HTTP*: Status 503" Here is the documentation for type mapping flex vs python: http://pyamf.org/architecture/typemap.html, pyamf takes python data types so I a

Re: [Numpy-discussion] Serializing numpy record array

On Sun, Jun 13, 2010 at 19:52, Vishal Rana wrote: > I created a record array (from strings and floats) with no dtype defined as: > ra = np.core.records.fromrecords(sq_list, names=("a", "b", "c")) > ra.a is found to be of type numpy.float64, when I serialize it using pyamf > under Mac OS X it works

Re: [Numpy-discussion] Installing numpy on py 3.1.2 , osx

On 06/14/2010 08:10 AM, Vincent Davis wrote: > > I kinda get that, I posted on the nose list ask what source/version to > install. I installed the most recent. They have a special branch for py3k support, I think you have to use that, cheers, David __

[Numpy-discussion] Serializing numpy record array

I created a record array (from strings and floats) with no dtype defined as: ra = np.core.records.fromrecords(sq_list, names=("a", "b", "c")) ra.a is found to be of type numpy.float64, when I serialize it using pyamf under Mac OS X it works great but under ubuntu 10.04 it fails. Looks like serial

Re: [Numpy-discussion] Installing numpy on py 3.1.2 , osx

On Sun, Jun 13, 2010 at 5:06 PM, David Cournapeau wrote: > > > On Mon, Jun 14, 2010 at 5:17 AM, Vincent Davis > wrote: >> >> As an update. I was able to get py 3.2.1 current source to build/install. >> After that I was able to build and install the current numpy. Everything >> seems ok. >> I did

Re: [Numpy-discussion] Installing numpy on py 3.1.2 , osx

On Mon, Jun 14, 2010 at 5:17 AM, Vincent Davis wrote: > As an update. I was able to get py 3.2.1 current source to build/install. > After that I was able to build and install the current numpy. Everything > seems ok. > I did try to run the tests but get an error. It looks like nose has a > problem

Re: [Numpy-discussion] Tensor contraction

Friedrich Romstedt wrote: > 2010/6/13 Alan Bromborsky : > >> I am writing symbolic tensor package for general relativity. In making >> symbolic tensors concrete >> I generate numpy arrays stuffed with sympy functions and symbols. >> > > That sound's interesting. > > >> The >> operations

Re: [Numpy-discussion] Installing numpy on py 3.1.2 , osx

As an update. I was able to get py 3.2.1 current source to build/install. After that I was able to build and install the current numpy. Everything seems ok. I did try to run the tests but get an error. It looks like nose has a problem. >>> np.test() Running unit tests for numpy Traceback (most rec

Re: [Numpy-discussion] Tensor contraction

Is this not what core.numeric.tensordotdoes? DG On Sun, Jun 13, 2010 at 12:37 PM, Friedrich Romstedt < friedrichromst...@gmail.com> wrote: > 2010/6/13 Alan Bromborsky : > > I am writing symbolic tensor package for general relativity

Re: [Numpy-discussion] Tensor contraction

2010/6/13 Alan Bromborsky : > I am writing symbolic tensor package for general relativity.  In making > symbolic tensors concrete > I generate numpy arrays stuffed with sympy functions and symbols. That sound's interesting. > The > operations are tensor product > (numpy.multiply.outer), permutati

Re: [Numpy-discussion] Tensor contraction

Friedrich Romstedt wrote: > 2010/6/13 Pauli Virtanen : > >> def tensor_contraction_single(tensor, dimensions): >>"""Perform a single tensor contraction over the dimensions given""" >>swap = [x for x in range(tensor.ndim) >>if x not in dimensions] + list(dimensions) >>x =

Re: [Numpy-discussion] Tensor contraction

2010/6/13 Pauli Virtanen : > def tensor_contraction_single(tensor, dimensions): >    """Perform a single tensor contraction over the dimensions given""" >    swap = [x for x in range(tensor.ndim) >            if x not in dimensions] + list(dimensions) >    x = tensor.transpose(swap) >    for k in r

Re: [Numpy-discussion] Possible bug: uint64 + int gives float64

Den 13.06.2010 18:19, skrev Charles R Harris: > > It's the combination of unsigned with signed that causes the > promotion. The int64 type can't hold the largest values in uint64. > Strictly speaking, doubles can't hold either of the 64 bit integer > types without loss of precision but at least

Re: [Numpy-discussion] Possible bug: uint64 + int gives float64

On Sun, Jun 13, 2010 at 9:20 AM, Pearu Peterson wrote: > On Sun, Jun 13, 2010 at 4:45 PM, Nadav Horesh > wrote: > > int can be larger than numpy.int64 therefore it should be coerced to > float64 (or float96/float128) > > Ok, I see. The results type is defined by the types of operands, not > by th

Re: [Numpy-discussion] Possible bug: uint64 + int gives float64

On Sun, Jun 13, 2010 at 4:45 PM, Nadav Horesh wrote: > int can be larger than numpy.int64 therefore it should be coerced to float64 > (or float96/float128) Ok, I see. The results type is defined by the types of operands, not by their values. I guess this has been discussed earlier but with small

Re: [Numpy-discussion] Possible bug: uint64 + int gives float64

int can be larger than numpy.int64 therefore it should be coerced to float64 (or float96/float128) Nadav -Original Message- From: numpy-discussion-boun...@scipy.org on behalf of Pearu Peterson Sent: Sun 13-Jun-10 12:08 To: Discussion of Numerical Python Subject: [Numpy-discussion] Poss

Re: [Numpy-discussion] PyArray_Scalar() and Unicode

Sat, 12 Jun 2010 17:33:13 -0700, Dan Roberts wrote: [clip: refactoring PyArray_Scalar] > There are a few problems with this. The biggest problem for me is > that it appears PyUCS2Buffer_FromUCS4() doesn't produce UCS2 at all, but > rather UTF-16 since it produces surrogate pairs for code point

[Numpy-discussion] Numpy, swig and docstring

Hi folks, I am trying to wrap a library with swig, distutils and numpy, and am facing troubles. In fact, swig documentation mention that it is possible to mention a module docsstring in the %module directive : %module(docstring="This is the example module's docstring") example where example is t

Re: [Numpy-discussion] NumPy re-factoring project

Sun, 13 Jun 2010 06:54:29 +0200, Sturla Molden wrote: [clip: memory management only in the interface] You forgot views: if memory management is done in the interface layer, it must also make sure that the memory pointed to by a view is never moved around, and not freed before all the views are f

[Numpy-discussion] Possible bug: uint64 + int gives float64

Hi, I just noticed some weird behavior in operations with uint64 and int, heres an example: >>> numpy.uint64(3)+1 4.0 >>> type(numpy.uint64(3)+1) Pearu ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/l