Re: [Numpy-discussion] Strange PyArray_FromObject() behavior

2012-02-16 Thread Val Kalatsky 
Hi Bill,

Looks like you are running a very fresh version of numpy.
Without knowing the build version and what's going on in the extension
module I can't tell you much.
The usual suspects would be:
1) Numpy bug, not too likely.
2) Incorrect use of PyArray_FromObject, you'll need to send more info.
3) Something is seriously corrupted, probably not the case, because
segfault would follow quickly.

Please provide more info.
Val

PS Is it something related to what we'll be working on (Trilinos)?


On Thu, Feb 16, 2012 at 11:09 AM, Spotz, William F wfsp...@sandia.govwrote:

  I have a user who is reporting tests that are failing on his platform.
  I have not been able to reproduce the error on my system, but working with
 him, we have isolated the problem to unexpected results when
 PyArray_FromObject() is called.  Here is the chain of events:

  In python, an integer is calculated.  Specifically, it is

  len(result.errors) + len(result.failures)

  where result is a unit test result object from the unittest module.  I
 had him verify that this value was in fact a python integer.  In my
 extension module, this PyObject gets passed to the PyArray_FromObject()
 function in a routine that comes from numpy.i.  What I expect, and what I
 typically get, is a numpy scalar array of type C long.  I had my user print
 the result using PyObject_Print() and what he got was

  array([0:00:00], dtype=timedelta64[us])

  I am stuck as to why this might be happening.  Any ideas?

  Thanks

  ** Bill Spotz  **
 ** Sandia National Laboratories  Voice: (505)845-0170  **
 ** P.O. Box 5800 Fax:   (505)284-0154  **
 ** Albuquerque, NM 87185-0370Email: wfsp...@sandia.gov **


 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion


___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Strange PyArray_FromObject() behavior

2012-02-16 Thread Charles R Harris 
On Thu, Feb 16, 2012 at 10:09 AM, Spotz, William F wfsp...@sandia.govwrote:

  I have a user who is reporting tests that are failing on his platform.
  I have not been able to reproduce the error on my system, but working with
 him, we have isolated the problem to unexpected results when
 PyArray_FromObject() is called.  Here is the chain of events:

  In python, an integer is calculated.  Specifically, it is

  len(result.errors) + len(result.failures)

  where result is a unit test result object from the unittest module.  I
 had him verify that this value was in fact a python integer.  In my
 extension module, this PyObject gets passed to the PyArray_FromObject()
 function in a routine that comes from numpy.i.  What I expect, and what I
 typically get, is a numpy scalar array of type C long.  I had my user print
 the result using PyObject_Print() and what he got was

  array([0:00:00], dtype=timedelta64[us])


That's strange. Is the output always a zero and the type a timedelta64? In
the absence of better info I'd quess a stray pointer or, unlikely, byte
order. The numpy version would be nice to know. If you have an old version
of numpy you could also give it a shot to see what happens.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion