I confirm that the reference count is consistent when trying the exemple
given in the first post of the ticket (Ubuntu 7.10, gcc 4.1.3, Python 2.5.1
).
Matthieu
2008/3/21, Jarrod Millman [EMAIL PROTECTED]:
On Thu, Mar 20, 2008 at 1:27 PM, Pauli Virtanen [EMAIL PROTECTED] wrote:
to,
Thank you, Pauli. Tested and applied in r4899.
Regards
Stéfan
On Thu, Mar 20, 2008 at 9:27 PM, Pauli Virtanen [EMAIL PROTECTED] wrote:
to, 2008-03-20 kello 21:09 +0100, Matthieu Brucher kirjoitti:
Well, it is not completely solved. With the patch, the reference count
keeps on raising,
ke, 2008-03-19 kello 11:53 -0700, Jarrod Millman kirjoitti:
Hello,
Thanks to everyone who has been working on getting the 1.0.5 release
of NumPy out the door. Since my last email at least 12 bug tickets
have been closed. There are a few remaining issues with the trunk,
but we are fasting
Well, it is not completely solved. With the patch, the reference count keeps
on raising, but as it is for Python scalars, it is not a problem, but the
underlying problem in Py_DECREF will show up eventually and it will need to
be solved. But I'm afraid I'm not intimate enough with the mecanisms of
to, 2008-03-20 kello 21:09 +0100, Matthieu Brucher kirjoitti:
Well, it is not completely solved. With the patch, the reference count
keeps on raising, but as it is for Python scalars, it is not a
problem, but the underlying problem in Py_DECREF will show up
eventually and it will need to be
Hello,
Thanks to everyone who has been working on getting the 1.0.5 release
of NumPy out the door. Since my last email at least 12 bug tickets
have been closed. There are a few remaining issues with the trunk,
but we are fasting approaching a release.
One additional issue that I would like to
