John Hunter wrote:
"Charlie" == Charlie Moad <cwmoad@...149...> writes:
>> 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?
John,
I agree that it is time for a new release.
The changes I have been making involving not rendering things with alpha == 0 or linewidth == 0 are certainly not complete, but I don't think this is a showstopper. Anything using agg should be OK, postscript is OK, svg is OK with linewidth == 0, which I think is what matters most immediately--some things rely on this. Help from other developers will be needed for other backends.
A new quiver could come before or after a release. I have not committed anything yet. I would like to be able to start doing so fairly soon, but in a way that does not cause trouble with a release. (At present, I am calling the new version quiver2 so that I can work with the pylab interface without clobbering the original version. The API will differ from that of the original, so maybe both should be present, with different names, for a while.) It would help to know when the actual production of the release is likely to occur, of course.
Eric
···
> On 6/2/06, David S. <davidschein@...423...> wrote:
Sounds like we could push 0.87.3 tomorrow or Tuesday. I personally
think the new quiver should be held off until 0.88 and it should
replace the old one if it is truly better.
- Charlie
···
On 6/4/06, Eric Firing <efiring@...229...> wrote:
John Hunter wrote:
>>>>>>"Charlie" == Charlie Moad <cwmoad@...149...> writes:
>
> > On 6/2/06, David S. <davidschein@...423...> 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?
John,
I agree that it is time for a new release.
The changes I have been making involving not rendering things with alpha
== 0 or linewidth == 0 are certainly not complete, but I don't think
this is a showstopper. Anything using agg should be OK, postscript is
OK, svg is OK with linewidth == 0, which I think is what matters most
immediately--some things rely on this. Help from other developers will
be needed for other backends.
A new quiver could come before or after a release. I have not committed
anything yet. I would like to be able to start doing so fairly soon, but
in a way that does not cause trouble with a release. (At present, I am
calling the new version quiver2 so that I can work with the pylab
interface without clobbering the original version. The API will differ
from that of the original, so maybe both should be present, with
different names, for a while.) It would help to know when the actual
production of the release is likely to occur, of course.