n't. Is this a bug in the test,
or does it indicate a 64-bit issue that is making inf/NaN
appear where it shouldn't? E.g., there are arpack errors,
but I don't know what the "Error info=-8" message signifies.
Other arpack errors are due to large solution m
Bruce Southey wrote:
On Fri, Feb 26, 2010 at 6:59 PM, David Warde-Farley wrote:
> On 26-Feb-10, at 7:43 PM, Charles سمير Doutriaux
> wrote:
>
>> Any idea on how to build a pure 32bit numpy on snow leopard?
>
> If I'm not mistaken you'll probably want to build against the
> Python.org Python rat
Hi-
I've been testing Python-2.7a3 on Mac OS 10.6.2. NumPy-1.4.0 will
not install; it appears something has changed within distutils that
breaks it:
$ export MACOSX_DEPLOYMENT_TARGET=10.6
$ export CFLAGS="-arch x86_64"
$ export FFLAGS="-m64"
$ export LDFLAGS="-Wall -undefined dynamic_lookup -bu
Pearu-
> smll_offset = smll_offset
> exec `smll_offset.__doc__`
Thanks for the quick and helpful response! I'll give it
a try. I don't grasp why it works, though. I suppose I don't
need to, but... I'm guessing the exec adds stuff to the current
namespace that isn't there until a fortran objec
Hi folks-
Can anyone offer any tips on how I can get epydoc to produce
API documentation for functions in an f2py-produced module?
Currently they get listed in the generated docs as "Variables":
Variables
psigc =
sigctp =
smll_offset =
Yet each of these objects is cal
Quoting Nick Fotopoulos <[EMAIL PROTECTED]>:
> Another oversight is that digest-mode subscribers were imported as
> regular subscribers. However, this is easily fixed at http://
> projects.scipy.org/mailman/listinfo/numpy-discussion.
Also, the original list passwords apparently were not/coul
