Numpy 1.0b2 was released last night and Travis hopes this
> will remain binary compatible with numpy 1.0. Are there
> any objections to a minor release bump? I could do this
> an soon as tomorrow.
Let's shoot for Tuesday evening, in advance of scipy. I'm going to
make one more attempt before then to get the damned widget lock
working right....
JDH
I hate to raise this issue again, but what is the status of the next release?
On Monday 14 August 2006 17:48, John Hunter wrote:
> Numpy 1.0b2 was released last night and Travis hopes this
> will remain binary compatible with numpy 1.0. Are there
> any objections to a minor release bump? I could do this
> an soon as tomorrow.Let's shoot for Tuesday evening, in advance of scipy. I'm going to
make one more attempt before then to get the damned widget lock
working right....
Seeing numpy b3 and then b4 has made me hesitate. I posted a snapshot
to the user list a while back just in case anyone wanted it. Have
these minor releases been breaking the c-api?
- Charlie
On 8/29/06, Darren Dale <dd55@...143...> wrote:
On Monday 14 August 2006 17:48, John Hunter wrote:
>
> > Numpy 1.0b2 was released last night and Travis hopes this
> > will remain binary compatible with numpy 1.0. Are there
> > any objections to a minor release bump? I could do this
> > an soon as tomorrow.
>
> Let's shoot for Tuesday evening, in advance of scipy. I'm going to
> make one more attempt before then to get the damned widget lock
> working right....I hate to raise this issue again, but what is the status of the next release?
I think b4 included the improved support for migrating from numarray. I'm not
sure it would have effected an mpl release.
Travis, would you care to comment?
On Tuesday 29 August 2006 14:07, Charlie Moad wrote:
On 8/29/06, Darren Dale <dd55@...143...> wrote:
> On Monday 14 August 2006 17:48, John Hunter wrote:
> >
> > > Numpy 1.0b2 was released last night and Travis hopes this
> > > will remain binary compatible with numpy 1.0. Are there
> > > any objections to a minor release bump? I could do this
> > > an soon as tomorrow.
> >
> > Let's shoot for Tuesday evening, in advance of scipy. I'm going to
> > make one more attempt before then to get the damned widget lock
> > working right....
>
> I hate to raise this issue again, but what is the status of the next
> release?Seeing numpy b3 and then b4 has made me hesitate. I posted a snapshot
to the user list a while back just in case anyone wanted it. Have
these minor releases been breaking the c-api?
He made a comment on the numpy list. We can shoot for a mpl release
by the end of the week. Are there any lingering issues?
- Charlie
On 8/29/06, Darren Dale <dd55@...143...> wrote:
On Tuesday 29 August 2006 14:07, Charlie Moad wrote:
> On 8/29/06, Darren Dale <dd55@...143...> wrote:
> > On Monday 14 August 2006 17:48, John Hunter wrote:
> > >
> > > > Numpy 1.0b2 was released last night and Travis hopes this
> > > > will remain binary compatible with numpy 1.0. Are there
> > > > any objections to a minor release bump? I could do this
> > > > an soon as tomorrow.
> > >
> > > Let's shoot for Tuesday evening, in advance of scipy. I'm going to
> > > make one more attempt before then to get the damned widget lock
> > > working right....
> >
> > I hate to raise this issue again, but what is the status of the next
> > release?
>
> Seeing numpy b3 and then b4 has made me hesitate. I posted a snapshot
> to the user list a while back just in case anyone wanted it. Have
> these minor releases been breaking the c-api?I think b4 included the improved support for migrating from numarray. I'm not
sure it would have effected an mpl release.Travis, would you care to comment?
There is this tk unicode nonsense in setupext.py.
I was hoping to get these build warnings taken care of on Linux (see my recent
post), but its not important.
On Tuesday 29 August 2006 15:21, Charlie Moad wrote:
We can shoot for a mpl release by the end of the week. Are there any
lingering issues?