On Fri, Apr 17, 2009 at 9:25 AM, Dan S
> wrote:
> Hi -
>
> I have written a numpy extension which works fine but has a memory
> leak. It takes a single array argument and returns a single scalar.
> After reducing the code down in order to chase the problem, I have the
> following:
>
> static PyOb
On Fri, Apr 17, 2009 at 7:37 PM, Charles R Harris wrote:
>
>
> On Fri, Apr 17, 2009 at 9:25 AM, Dan S
>
> > wrote:
>
>> Hi -
>>
>> I have written a numpy extension which works fine but has a memory
>> leak. It takes a single array argument and returns a single scalar.
>> After reducing the code
On Fri, Apr 17, 2009 at 9:25 AM, Dan S
> wrote:
> Hi -
>
> I have written a numpy extension which works fine but has a memory
> leak. It takes a single array argument and returns a single scalar.
> After reducing the code down in order to chase the problem, I have the
> following:
>
> static PyOb
1) Calling both PyArray_XDECREF(array) and Py_DECREF(array) is likely wrong.
2) Py_DECREF(input) should never be done.
On Fri, Apr 17, 2009 at 12:25 PM, Dan S wrote:
> Hi -
>
> I have written a numpy extension which works fine but has a memory
> leak. It takes a single array argument and returns
> In article
> <5b8d13220904161842k2f2f76c9v1dde62f4655c2...@mail.gmail.com>,
> David Cournapeau wrote:
>
> > It is a bug of bdist_mpkg on leopard (the error message is a bit
> > misleading - if you look at the code, you will see it calls for a
> > command line utility which does not exist on l
In article
<5b8d13220904161842k2f2f76c9v1dde62f4655c2...@mail.gmail.com>,
David Cournapeau wrote:
> On Fri, Apr 17, 2009 at 4:55 AM, Russell E. Owen
> wrote:
> > Does anyone have a binary installer for numpy 1.3.0 and Python 2.6?
> >
> > I've been able to install from source and all tests pas
Got it - Thanks
Gerry
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Stéfan van der Walt
Sent: Friday, April 17, 2009 8:42 AM
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Indexing
Hi Gerry
2009/
I know this is the wrong forum, but:
Yet another reason Python itself needs a standard, supported way to
handle package versioning.
*sigh*
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959 voice
7600 Sand Point Way NE (20
Hi -
I have written a numpy extension which works fine but has a memory
leak. It takes a single array argument and returns a single scalar.
After reducing the code down in order to chase the problem, I have the
following:
static PyObject * kdpee_pycall(PyObject *self, PyObject *args)
{
Py
Hi Gerry
2009/4/17 Talbot, Gerry :
> I stumbled across this anomaly, the assignment to ncycle[i][b] fails, yet
> ncycle[:][b] works and the final print works. Is this a known bug or
> limitation ? I am running numpy-1.2.1 with python 2.5.4
The fancy indexing (indexing with an array) in ncycle[i
Hi,
I stumbled across this anomaly, the assignment to ncycle[i][b] fails,
yet ncycle[:][b] works and the final print works. Is this a known bug
or limitation ? I am running numpy-1.2.1 with python 2.5.4
Gerry
from numpy import *
ncycle = arange(10)
i = array([0, 1, 2, 3, 4, 5
On 4/17/2009 11:50 AM, Gael Varoquaux wrote:
> Could you elaborate on your reason.
Probably silly reasons though...
I have a distutils.cfg file and a build system set up that works. I
don't want to bother setting up a different build system when I already
have one that works. I can use the Int
On Fri, Apr 17, 2009 at 11:48:57AM +0200, Sturla Molden wrote:
> I use this 32 bit mingw binary to build my Cython and f2py extensions. I
> works like a charm. I have licenses for Intel compilers at work, but I
> prefer gfortran 4.4.
Could you elaborate on your reason.
Gaël
On 4/17/2009 10:50 AM, David Cournapeau wrote:
> I think Matthieu meant you have to use VS2003 as a MS compiler. Mingw is
> obviously fine, since that's how numpy binaries are built for quite a
> long time
That is what I thought he meant as well, and it seems to be a widespread
belief. The fact
Sturla Molden wrote:
> On 4/15/2009 6:44 PM, Matthieu Brucher wrote:
>
>
>> There is a Python limitation for the compiler.
>>
>
> There is a common misunderstanding that only VS2003 can be used to
> compile extension objects for Python 2.5. Don't believe it. There is no
> Python limitati
On 4/15/2009 6:44 PM, Matthieu Brucher wrote:
> There is a Python limitation for the compiler.
There is a common misunderstanding that only VS2003 can be used to
compile extension objects for Python 2.5. Don't believe it. There is no
Python limitation for the compiler.
There is a Python limit
You actually need the package unpacked to use scipy.weave and make C
extensions which use Numpy's .h files.
We have found that Numpy + Scipy are perfectly zip-safe for users but
not for developers.
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun
Yes,
Thanks for all your support, it works a treat. My conclusion is that the
.exe release for Windows are sufficient for our needs.
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Charles R
Harris
Sent: 17 Apri
18 matches
Mail list logo
