We also have a number of centos boxes here at NYU astronomy and we've
been in dependency hell trying to get everything to work without
failing tests (mainly scipy more than numpy). Any help greatly
appreciated.
Erin
On 5/3/07, Fabian Braennstroem <[EMAIL PROTECTED]> wrote:
> Hi Neal,
>
> * Neal
On Wednesday 09 May 2007 08:54:37 Bernhard Voigt wrote:
> I'm trying to subclass ndarray or recarray to build a record array that has
> a dictionary with a mapping of keys to array indexes and vice versa.
Bernhard,
Could you send me the rest of your code ? I'd like to test a couple of things
bef
Tom Denniston wrote:
> So searchsorted is supposed to take a list. The arguments I am using
> are not correct.
No, it will take a scalar value to search for, too.
In [18]: numpy.searchsorted(numpy.array([1, 2, 3, 4]), 1)
Out[18]: 0
In [19]: numpy.searchsorted(numpy.array(['1', '2', '3', '4']),
So searchsorted is supposed to take a list. The arguments I am using
are not correct. But it still seems strange to me that these
incorrect params trigger a memory error. Is a check simply missing or
is this possibly a sign of a larger bug? I can simply correct my
params so this is no big deal,
Hi all -
I've been trying to set up configuration files to standardize a local
1.02numpy installation and have run into a problem with the intel
compiler
package. If I try
python setup.py config_fc --fcompiler=intel build_ext
(from the top level numpy-1.0.2 directory) I get the following failur
I'm trying to subclass ndarray or recarray to build a record array that has
a dictionary with a mapping of keys to array indexes and vice versa. I come
across the problem, that depending on the field access method I get
different types back:
# a is a sublcass of record array
print type(a)
pr
