Re: Python: Numeric vs NumArray vs Numpy (itkPyBuffer)

[Mathieu Malaterre <mathieu.malaterre@gmail.com>]

Steve,

2009/9/29 Gaëtan Lehmann <gaetan.lehmann@jouy.inra.fr>:
>
> Le 29 sept. 09 à 09:27, Mathieu Malaterre a écrit :
>
>> Hi there,
>>
>>  I am reading through the code of itkPyBuffer and found:
>>
>> $ cat Wrapping/WrapITK/ExternalProjects/PyBuffer/itkPyBuffer.txx
>> ...
>> // Deal with slight incompatibilites between NumPy (the future,
>> hopefully),
>> // Numeric (old version) and Numarray's Numeric compatibility module (also
>> old).
>> #ifndef NDARRAY_VERSION
>> // NDARRAY_VERSION is only defined by NumPy's arrayobject.h
>> // In non NumPy arrayobject.h files, PyArray_SBYTE is used instead of
>> BYTE.
>> #define PyArray_BYTE PyArray_SBYTE
>> #endif
>> ...
>>
>>  There will be an issue soon in debian as python-numarray is
>> deprecated so we need to transition -hopefully- to numpy.
>>
>> A couple of questions:
>> - Does anyone use Numpy ? Is this working ?
>
> I do - it works.
>
>> - What is the difference in between (the patched)
>> Wrapping/WrapITK/ExternalProjects/PyBuffer/itkPyBuffer.txx and
>> Wrapping/CSwig/CommonA/itkPyBuffer.txx ?
>
>
> I never succeeded to use the later, while the former works great :-)
> The new one is a rework of what was began with the old one, but never
> polished enough to be production ready.


What do you think ? Should we just wait until ITK_WRAP_ITK becomes the
default ?
Or use the old CSWIG approach and just re-activate NUMARRAY using
NUMPY (it does compile, I tested it), knowing that it is not
'production ready' ?

-- 
Mathieu