Hi all,
Can someone reproduce the failure
with
numpy.__version__
'1.2.0.dev5618'
==
FAIL: Test corrcoef 1 1D variable w/missing values
--
Traceback (most
Hi all,
I'm trying to get scipy to recognize my FFTW install. I know there is
another thread on this, but I didn't understand the discussion fully.
Which file do I modify to let scipy know where my FFTW install is?
As a possibly related note, running scipy.config() and
You shoud edit site.cfg file: look for site.cfg.example and follow the
instructions.
Nadav
On Thu, 2008-08-07 at 01:33 -0700, [EMAIL PROTECTED] wrote:
Hi all,
I'm trying to get scipy to recognize my FFTW install. I know there is
another thread on this, but I didn't understand the
Nils,
==
FAIL: Test corrcoef 1 1D variable w/missing values
--
...
/data/home/nwagner/local/lib/python2.5/site-packages/numpy/testing/utils.p
y, line 289, in
I'm pleased to announce that Enthought has released the Enthought Python
Distribution (EPD) 2.5.2001 for OS X!
EPD is a Distribution of the Python Programming Language (currently
version 2.5.2) that includes over 60 additional libraries, including ETS
2.7.1. Please visit the EPD website
Hello all,
I have a bizarre bug that causes numpy to segfault, but:
- only when run under ipython
- only when numpy is imported *after* an other library (that does
not import numpy)
Here's what the code looks like.
Crashes (only in ipython):
import celltool.utility.pil_lite.Image as Image,
Hmm, I may have identified this by other means. See my next email...
Zach
On Aug 7, 2008, at 3:22 PM, Zachary Pincus wrote:
Hello all,
I have a bizarre bug that causes numpy to segfault, but:
- only when run under ipython
- only when numpy is imported *after* an other library (that does
That seems to have changed something for sure.
I created a modified site.cfg file. When I run system_info.py I get this
message
fftw_info:
libraries fftw3 not found in c:\FFTW
libraries fftw3 not found in C:\Python25\lib
libraries fftw3 not found in C:\
libraries fftw3 not found in
Hi,
I am unable to specify a dtype when using numpy.rec.fromrecords. This
problem only occurs when one of the dtypes is an object. (Please see
below)
Thanks in advance for your help.
Sameer
In [7]: import datetime, numpy as np
In [8]: print np.__version__
1.2.0.dev5253
In [9]:
Hello all,
As per my previous email, I encountered a strange sometimes-segfault
when using 'numpy.array(thing)' to convert 'thing' (which provides an
__array_interface__) to a numpy array.
The offending __array_interface__ has a 'data' item that is a python
string (not, as specified in the
Hello all,
numpy.unpackbits has a docstring that states that it returns a boolean
array, but the function instead returns a uint8 array. Should I enter
this in trac as a documentation bug or a functionality bug?
Also, numpy.packbits will not accept a bool-typed array as input (only
Hello,
the following code drives python into an endless loop :
import numpy
numpy.fromstring(abcd, dtype = float, sep = ' ')
I think the function numpy.fromstring is lacking an adequate error handling for
that case.
Is it a bug ?
Regards,
--
O.C.
Python 2.5.2
Debian Lenny
Créez
the following code drives python into an endless loop :
import numpy
numpy.fromstring(abcd, dtype = float, sep = ' ')
It works on OS X 10.5.4 with a today's SVN head of numpy:
In [1]: import numpy
In [2]: numpy.fromstring(abcd, dtype = float, sep = ' ')
Out[2]: array([ 0.])
In [3]:
13 matches
Mail list logo
