numpy-discussion

[Numpy-discussion] NumPy 1.0b1 at the door...

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

I'm getting ready to tag the trunk as the 1.0b1 release (will be done in 
2 hours unless I hear from somebody).    I've taken care of most of the 
relevant open tickets.  Some of the build issues are still there but 
they can be fixed during the beta release period which I expect to be 
several months.


-Travis

Re: [Numpy-discussion] NumPy 1.0b1 at the door...

[Robert K. <rob...@gm...>]

Travis Oliphant wrote:
> I'm getting ready to tag the trunk as the 1.0b1 release (will be done in 
> 2 hours unless I hear from somebody).    I've taken care of most of the 
> relevant open tickets.  Some of the build issues are still there but 
> they can be fixed during the beta release period which I expect to be 
> several months.

I'm testing the change from using pkgload in __init__ to explicit imports now. 
If you can hold off until I finish with that, I'd appreciate it.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco

Re: [Numpy-discussion] NumPy 1.0b1 at the door...

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

Stefan van der Walt wrote:
> Hi Travis
>
> Albert and I are busy doing some final beta testing.  Quick question:
> can Fortran-order arrays be contiguous, ever?
>
> In [62]: N.empty((3,3),order='F').flags['CONTIGUOUS']
> Out[62]: False
>   

Thank you very much for the testing.  You two have been amazingly helpful.

No.  CONTIGUOUS means "C-CONTIGUOUS"

Now, 0-d and 1-d arrays can be both Fortran-contiguous *and* 
C-contiguous which is why "FNC" exists to test against that case.


-Travis