Re: [pygsl-discuss] Patches and isnull

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

On Wed, Nov 12, 2008 at 03:34:02PM +0100, Pierre SCHNIZER wrote:
> You can suscribe to the list on:
> 	http://lists.sourceforge.net/lists/listinfo/pygsl-discuss

Sorry, perhaps a link to that page should be on the homepage
(http://pygsl.sourceforge.net/) I suppose I should know how to sign up
with just the list address (which is on the homepage), but...

> W. Trevor King wrote:
> >I was running into some problems with run_tests.py on my PyGSL
> >installation from the CVS source.  I fixed some missing modules
> >problems by forcing a SWIG regeneration, and since I used SWIG 1.3.33
> >and the source was originally SWIG 1.3.29, I thought I'd pass some
> >patches back upstream.  Can I attach them and send them to this list?
> >The patch section of the sourceforge site looks unused...
> This would be very much appreciated. You can either send the patch to 
> the list or add the patch at sf. Please always drop a line to the list 
> if you add something on the patch side. I overlooked a nices patch for 
> the last release (but it is in CVS now.)

Patches attached.

> >Once I got all the modules installed, I noticed I was getting errors
> >during block_test.py spewing some messages about test_2_isnull and failed
> >array type sanity checks.  While I'm orienting myself in the code, I
> >thought I would ask and see if anyone else was having these problems.
> 
> Please could you send me the output of the test? Normally the test 
> should only fail for char arrays....

Output of
  python block_test.py > python_block_test.out 2>&1
attached, as well as that of
  python histogram_test.py 2> python_histogram_test.out

I'm not understanding my notes at the moment, I will dig in some more
and report back once I've straigtened myself out...

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