On 03/17/2012 04:00 PM, Sandro Tosi wrote:
> On Sat, Mar 17, 2012 at 00:09, Sandro Tosi <morph@debian.org> wrote:
>> On Fri, Mar 16, 2012 at 15:05, Sandro Tosi <morph@debian.org> wrote:
>>> Well, before I can say anything more I'll have to get my hands dirty.
>>
>> that I'm doing right away; I've committed your diff as you sent, and
>> I'm working on polishing it a bit, something including:
>>
>> - include dirs for py3k
>> - f2py for py3k
>> - tests are not run for python 3 interpreters
>>
>> just minor stuff like that.
>
> that stuff is done and the package is uploaded: Thanks for your contribution!
>
> Cheers,
thanks for updating numpy and adding py3.
There is a failure in the testsuite in experimental that doesn't occur
in testing. The build only works because the result of the tests are
ignored in rules (and it is not documented why).
Is this known?
Running unit tests for numpy
NumPy version 1.6.1
NumPy is installed in
/build/buildd-python-numpy_1.6.1-6-i386-lYkcLV/python-numpy-1.6.1/debian/tmp/usr/lib/python2.7/dist-packages/numpy
Python version 2.7.3rc1 (default, Mar 10 2012, 00:01:06) [GCC 4.6.3]
nose version 1.1.2
.........................Debug memory block at address p=0xaa13400: API 'm'
8 bytes originally requested
The 3 pad bytes at p-3 are FORBIDDENBYTE, as expected.
The 4 pad bytes at tail=0xaa13408 are FORBIDDENBYTE, as expected.
The block was made by call #1026630 to debug malloc/realloc.
Data at p: a3 03 00 00 00 00 00 00
Fatal Python error: bad ID: Allocated using API 'm', verified using API 'o'
Running unit tests for numpy
NumPy version 1.6.1
NumPy is installed in
/build/buildd-python-numpy_1.6.1-6-i386-lYkcLV/python-numpy-1.6.1/debian/tmp/usr/lib/python2.7/dist-packages/numpy
Python version 2.7.3rc1 (default, Mar 9 2012, 23:29:14) [GCC 4.6.3]
nose version 1.1.2
Aborted
Attachment:
signature.asc
Description: OpenPGP digital signature