numpy contains bug that causes segfault when using pylint

[yannek]

Binary package hint: python-numpy

numpy contained a bug that can cause a segfault in the python interpreter, which again can be triggered by pylint. This bug is konwn and fixed as documented upstream here:
http://projects.scipy.org/numpy/ticket/1464
I've hit this bug while using the versions of pylint, numpy from maverick. Making the use of pyreverse impossible on several packages.
The latest stable release of numpy (1.4.1) should contain the fixes, and is in debian testing.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-numpy 1:1.3.0-3build1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
Date: Thu Aug 19 12:42:05 2010
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: python-numpy

[Timmy Shih Jun Yee (shijun)]

The bug fix has been committed to trunk according to upstream.

[yannek (yannek-deactivatedaccount)]

Yes, I think so too. Unfortunatly the numpy version in maverick is still 1.3.0 and the fix was commited after that release.
I've tested it with debian testing/squeeze (numpy 1.4.1) and there the segfault does not occur. An update of the ubuntu package (plus a rebuild of the packages dependend on it) would be great.

[Timmy Shih Jun Yee (shijun)]

They're working on it (see bug 620734).

[yannek (yannek-deactivatedaccount)]

Thank you!

[Julian Taylor (jtaylor)]

should be fixed since natty