This is starting to bite enough people that we should consider rolling
out a release. We had hope to get the 3d stuff working before the
next release, but having a version up there that doesn't work with the
latest numpy is a more pressing problem to me. Does this seem like a
good idea to you Charlie? Are there other features or fixes that
other developers would like to get in first?
JDH
···
On 6/2/06, David S. <davidschein@...1128...> wrote:
>> I have just installed numpy-0.9.8, scipy-0.4.9, and
>> matplotlib-0.87.2 on a Windows machine with Python 2.4.2.
> matplotlib-0.87.2 requires numpy-0.9.6. You will get an
> error otherwise.
Agreed. I think we are tied closely enough to numpy that a minor
release is justified. A 0.88 release doesn't seem justified yet, so I
could push a 0.87.3 barring any outstanding bugs.
- Charlie
···
On 6/3/06, John Hunter <jdhunter@...4...> wrote:
> On 6/2/06, David S. <davidschein@...1128...> wrote:
>> I have just installed numpy-0.9.8, scipy-0.4.9, and
>> matplotlib-0.87.2 on a Windows machine with Python 2.4.2.
> matplotlib-0.87.2 requires numpy-0.9.6. You will get an
> error otherwise.
This is starting to bite enough people that we should consider rolling
out a release. We had hope to get the 3d stuff working before the
next release, but having a version up there that doesn't work with the
latest numpy is a more pressing problem to me. Does this seem like a
good idea to you Charlie? Are there other features or fixes that
other developers would like to get in first?