Re: [pygsl-discuss] Patches and isnull

[W. T. K. <wk...@dr...>]

I remembered what I did to get more info about the block_test
failures.

First, I increased the verbosity of block_test.py:

diff --git a/tests/block_test.py b/tests/block_test.py
index ae400ab..91cc813 100644
--- a/tests/block_test.py
+++ b/tests/block_test.py
@@ -14,7 +14,7 @@ from array_check import myord, myorda, array_check
 import unittest
 import sys
 sys.stderr = sys.stdout
-#pygsl.set_debug_level(10)
+pygsl.set_debug_level(10)
     
 def getopentmpfile(mode='rb'):
     file = tempfile.TemporaryFile(mode)

Then I ran
$ python block_test.py > python_block_test.out 2>&1

The output was long (1.5 MB), so I grepped through it for the error I
expected.
$ grep -A 4 -B 4 'PyGSL_PyArray_Check' python_block_test.out | grep -A4 -B4 'array type'
which revealed the line (once for each error):
  In Function PyGSL_PyArray_Check from File src/init/block_helpers.c at line 221 Found an array type of 18 but expected 23

I compiled a program to print out the values of various
PyArray_<Types> and found that
  PyArray_STRING = 18
  PyArray_CHAR = 23

That is as far as I've gotten so far...

-- 
public key at http://www.physics.drexel.edu/~wking/pubkey.txt