Bill Baxter wrote:
If you do this:
numpy.linalg.eig(numpy.random.rand(3,3))
You'll (almost always) get a wrong answer back from numpy. Something
like:
(array([ 1.72167898, -0.07251007, -0.07251007]),
array([[ 0.47908847, 0.72095163, 0.72095163],
[ 0.56659142, -0.46403504,
Thanks for the info Nils. Sounds like it was fixed post-1.0b1. Good news.And Trac seems to be letting me in again. Not sure what was wrong there.--bbOn 8/18/06,
Nils Wagner [EMAIL PROTECTED] wrote:
Bill Baxter wrote: If you do this: numpy.linalg.eig(numpy.random.rand(3,3)) You'll (almost always)
On Fri, Aug 18, 2006 at 01:54:44PM +0900, David Cournapeau wrote:
import numpy as N
from ctypes import cdll, POINTER, c_int, c_uint
_hello = cdll.LoadLibrary('libhello.so')
_hello.sum.restype= c_int
_hello.sum.artype = [POINTER(c_int), c_uint]
def sum(data):
return
Hello all
snip
I decided to upgrade to 1.0b2 just to see what I get and now I get 7kB of
possibly lost memory, coming from PyObject_Malloc (in
/usr/lib/libpython2.4.so.1.0). This is a constant 7kB, however, and it
isn't getting any larger if I increase the loop iterations. Looks good
then.
Hello all
-Original Message-
From: [EMAIL PROTECTED] [mailto:numpy-
[EMAIL PROTECTED] On Behalf Of David Cournapeau
Sent: 18 August 2006 06:55
To: Discussion of Numerical Python
Subject: [Numpy-discussion] ctypes: how does load_library work ?
snip
That works OK, but to avoid the
Stefan van der Walt wrote:
On Fri, Aug 18, 2006 at 01:54:44PM +0900, David Cournapeau wrote:
import numpy as N
from ctypes import cdll, POINTER, c_int, c_uint
_hello = cdll.LoadLibrary('libhello.so')
_hello.sum.restype= c_int
_hello.sum.artype = [POINTER(c_int), c_uint]
def
Hi,
I'm starting to (slowly) replace numarray by NumPy at the core of PyTables,
specially at those places where the speed of NumPy is *much* better, that is,
in the creation of arrays (there are places in PyTables where this is
critical, most specially in indexation) and in copying arrays. In
Can you provide some details about your approach to migrating to
NumPy? Are you following some documentation on migration or do you
have your own plan of attack?
Chris
On Aug 18, 2006, at 6:59 AM, Francesc Altet wrote:
Hi,
I'm starting to (slowly) replace numarray by NumPy at the
A Divendres 18 Agost 2006 16:44, Chris Kees va escriure:
Can you provide some details about your approach to migrating to
NumPy? Are you following some documentation on migration or do you
have your own plan of attack?
Well, to say the truth none of both ;-). The truth is that I was
Chris Kees wrote:
Hi,
I just ran convertcode.py on my code (from the latest svn source
of numpy) and it looks like it just changed the import statements to
import numpy.oldnumeric as Numeric
So it doesn't look like it's really helping me move over to the
new usage. Is
Sebastian Haase wrote:
Hi,
array dtype descriptors have an attribute itemsize that gives the total
number of bytes required for an item of that dtype.
Scalar types, like numy.int32, also have that attribute,
but it returns something else - don't know what:
Furthermore there are
I realize it was just released, but is there going to be a windows release
for 1.02b?
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make
[EMAIL PROTECTED] wrote:
I realize it was just released, but is there going to be a windows release
for 1.02b?
There will be either be one of 1.0b3 or one of 1.0b2 released for
windows by Monday.
-Travis
-
Using
Sebastian Haase wrote:
On Friday 18 August 2006 11:38, Travis Oliphant wrote:
Sebastian Haase wrote:
Hi,
array dtype descriptors have an attribute itemsize that gives the total
number of bytes required for an item of that dtype.
Scalar types, like numy.int32, also have that
On Friday 18 August 2006 15:25, Travis Oliphant wrote:
Sebastian Haase wrote:
On Friday 18 August 2006 11:38, Travis Oliphant wrote:
Sebastian Haase wrote:
Hi,
array dtype descriptors have an attribute itemsize that gives the
total number of bytes required for an item of that dtype.
s_wsfe is not LAPACK's routine it's a routine from the g2c library.
You have to link it in in addition to lapack_lite.
Piotr
On Friday 18 August 2006 18:07, [EMAIL PROTECTED] wrote:
Hi,
I am correctly assuming that numpy needs the full lapack
distribution, and not just the few lapack
Sebastian Haase wrote:
On Friday 18 August 2006 15:25, Travis Oliphant wrote:
Sebastian Haase wrote:
On Friday 18 August 2006 11:38, Travis Oliphant wrote:
Sebastian Haase wrote:
Hi,
array dtype descriptors have an attribute itemsize that gives the
total number
This leak is caused by add_docstring, but it's supposed to leak. I wonder if
there's a way to register some kind of on-exit handler in Python so that
this can also be cleaned up?
import atexit
atexit.register(your_cleanup_function)
whose api is no args on input:
def your_cleanup_function():
On Fri, Aug 18, 2006 at 04:45:03PM +0200, Stefan van der Walt wrote:
Hi Norbert
On Fri, Aug 18, 2006 at 03:36:47PM +0200, Norbert Nemec wrote:
in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch
fixes the issue.
Please file a ticket so that we don't lose track of
Hi,
[PL]: s_wsfe is not LAPACK's routine it's a routine from the g2c library.
[PL]: You have to link it in in addition to lapack_lite.
Thanks for the pointer.
Sorry about my ignorance about these things. But is lapack_lite linked
to numpy even if you specify the full lapack library?
Hi All,
I've noticed a lot of trailing whitespace while browsing through the
numpy subversion repository. So here is a perl script I pinched from
the linux-kernel mailing list that does a good job of removing it.
Chuck
cleanfile
Description: Binary data
21 matches
Mail list logo
