Re: [Numpy-discussion] Release of 1.0 coming

[Travis O. <oli...@ie...>]

Albert Strasheim wrote:
> Hey Travis
>
>   
>> -----Original Message-----
>> From: num...@li... [mailto:numpy-
>> dis...@li...] On Behalf Of Travis Oliphant
>> Sent: Tuesday, October 24, 2006 12:32 AM
>> To: Discussion of Numerical Python
>> Subject: [Numpy-discussion] Release of 1.0 coming
>>
>> The long awaited day is coming....--- Wednesday is the target.
>>
>> Please submit problems before Tuesday (tomorrow).  Nothing but bug-fixes
>> are being changed right now.
>>     
>
> Some Valgrind warnings that you might want to look at:
> http://projects.scipy.org/scipy/numpy/ticket/360
>   
fixed.
> Maybe faltet could provide some code to reproduce this problem:
> http://projects.scipy.org/scipy/numpy/ticket/355
>   
Looked at it and couldn't see what could be wrong.   Need code to 
reproduce the problem.
> I think this ndpointer issue has been resolved (Stefan?):
> http://projects.scipy.org/scipy/numpy/ticket/340
>   
Yes it has.  Fixed.
> I think ctypes 1.0.1 is required for ndpointer to work, so we might consider
> some kind of version check + warning on import? 
>   
Not sure about that.  It worked for me using ctypes 1.0.0.
> Maybe a Python at-exit handler can be used to avoid the add_docstring leaks
> described here:
> http://projects.scipy.org/scipy/numpy/ticket/195
>   
I'm not too concerned about this.  Whether we release the memory right 
before exiting or just let the O.S. do it when the process quits seems 
rather immaterial.  It would be a bit of work to implement so the cost / 
benefit ratio seems way to high.
> Also, what's the story with f2py? It seems Pearu is still making quite a few
> changes in the trunk as part of F2PY G3.
>   
Pearu told me not to hold up NumPy 1.0 because f2py g3 is still a ways 
away.  His changes should not impact normal usage of f2py.   I suspect 
NumPy 1.0.1 will contain f2py g3

-Travis