Now that scipy 0.7.0b1 has been tagged, I wanted to start planning for
the NumPy 1.3.0:
http://projects.scipy.org/scipy/numpy/milestone/1.3.0
The original plan was to release 1.3 at the end of November. At this
point, we are going to have to push back the release date a bit. I
would like to get
Jarrod Millman wrote:
Now that scipy 0.7.0b1 has been tagged, I wanted to start planning for
the NumPy 1.3.0:
http://projects.scipy.org/scipy/numpy/milestone/1.3.0
For completeness, we were wondering with Jarrod if the main focus of
1.3 could be python 2.6 compatibility (plus what is
A Monday 24 November 2008, David Cournapeau escrigué:
Jarrod Millman wrote:
Now that scipy 0.7.0b1 has been tagged, I wanted to start planning
for the NumPy 1.3.0:
http://projects.scipy.org/scipy/numpy/milestone/1.3.0
For completeness, we were wondering with Jarrod if the main focus of
Well, talking about support to 2.6:
When using explicit outputs for some functions (eg, ma.max,
ma.min...), a value that should be masked is transformed into np.nan
when the explicit output is not a ma.MaskedArray. That worked great in
2.5, with np.nan automatically transformed when the
On Mon, Nov 24, 2008 at 4:34 AM, Jarrod Millman [EMAIL PROTECTED]wrote:
Now that scipy 0.7.0b1 has been tagged, I wanted to start planning for
the NumPy 1.3.0:
http://projects.scipy.org/scipy/numpy/milestone/1.3.0
The original plan was to release 1.3 at the end of November. At this
point,
David Cournapeau wrote:
Windows 64 is a PITA,
...
I don:t see much hope to see more than a simple numpy built with
lapack-lite. This could be useful for people who use numpy for
matplotlib, for example; not sure if it worths the trouble.
I think there is a great deal of use for it beyond
A Monday 24 November 2008, Jarrod Millman escrigué:
Now that scipy 0.7.0b1 has been tagged, I wanted to start planning
for the NumPy 1.3.0:
http://projects.scipy.org/scipy/numpy/milestone/1.3.0
The original plan was to release 1.3 at the end of November. At this
point, we are going to have
