[SciPy-user] [Numpy-discussion] [ANN] NumPy 0.9.6 released
mfmorss at aep.com
mfmorss at aep.com
Wed Mar 15 05:33:07 CST 2006
>We need some of these people to convert earlier than that, though, so we
>can make sure that 1.0 really is ready for prime time. I think it's
>very close already or the version number wouldn't be so high. We are
>just waiting for more people to start using it and report any issues
>that they have before going to 1.0 (I'd also like scalar math to be
>implemented pre 1.0 as well in case that requires any C-API additions).
I can understand that, but here as a potential industrial users of Numpy,
we can't really afford the risk. We're looking at Numpy as a key piece of
a Python replacement of commercial software for critical daily production.
If we build Numpy/Scipy into our system, it has to work. We don't want to
be anyone's beta testers.
Mark F. Morss
Principal Analyst, Market Risk
American Electric Power
<oliphant at ee.byu.
Sent by: SciPy Users List
numpy-discussion- <scipy-user at scipy.net>,
admin at lists.sourc numpy-discussion
eforge.net <numpy-discussion at lists.sourceforge
Re: [SciPy-user] [Numpy-discussion]
[ANN] NumPy 0.9.6 released
Paul Ray wrote:
>On Mar 14, 2006, at 1:33 PM, Travis Oliphant wrote:
>>>Just wondering, does this one also require an update to scipy?
>>>And in general do numpy updates always require an update to scipy,
>>>Or is it only when the numpy C API interface changes?
>>It's only when the C-API interface changes that this is necessary.
>>Pre-1.0 it is likely to happen at each release.
>>After that it is less likely to happen.
>Pre-1.0, I think it is fine for the version numbering to be a free-
>for-all, as it has been. There have been many times, it seems, where
>the latest numpy didn't work with the latest scipy and stuff like that.
The current SVN of numpy and the current SVN of scipy usually work with
each other (perhaps with only a day lag).
>After 1.0, I would like to encourage some discipline with regards to
>numpy version numbering. From 1.0, the API should NOT change at all
This is the plan and it is why we are being slow with getting 1.0 out.
But, we *need* people to try NumPy on their codes so that we can
determine whether or not API additions are needed. Without this testing
we are just guessing based on the developer's own codes which do not
cover the breadth.
>I think that many people with codes that use Numeric or numarray are
>awaiting the numpy 1.0 release as a sign that it is stable and ready
>for prime time, before converting their codes.
We need some of these people to convert earlier than that, though, so we
can make sure that 1.0 really is ready for prime time. I think it's
very close already or the version number wouldn't be so high. We are
just waiting for more people to start using it and report any issues
that they have before going to 1.0 (I'd also like scalar math to be
implemented pre 1.0 as well in case that requires any C-API additions).
Thanks for the feedback. What you described will be the basic behavior
once 1.0 is released.
Note that right now the only changes that usually need to be made are a
re-compile. I know this can still be annoying when you have a deep
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live
and join the prime developer group breaking into this new coding territory!
Numpy-discussion mailing list
Numpy-discussion at lists.sourceforge.net
More information about the Numpy-discussion