Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Thu, May 8, 2008 at 6:38 PM, Charles Doutriaux <[EMAIL PROTECTED]>
wrote:

> I don't think it is reasonable to say the trunk is in good shape when
> the power function does not work...
>
> Just my thoughts...
>

Is that ticket #301? What are you suggesting it do?

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles Doutriaux]

I don't think it is reasonable to say the trunk is in good shape when 
the power function does not work...

Just my thoughts...

C.

Charles R Harris wrote:
> Hi Jarrod,
>
> On Tue, May 6, 2008 at 2:40 AM, Jarrod Millman <[EMAIL PROTECTED] 
> > wrote:
>
> Hey,
>
> The trunk is in pretty good shape and it is about time that I put out
> an official release.  So tomorrow (in a little over twelve hours) I am
> going to create a 1.1.x branch and the trunk will be officially open
> for 1.2 development.  If there are no major issues that show up at the
> last minute, I will tag 1.1.0 twenty-four hours after I branch.  As
> soon as I tag the release I will ask the David and Chris to create the
> official Windows and Mac binaries.  If nothing goes awry, you can
> expect the official release announcement by Monday, May 12th.
>
> In order to help me with the final touches, would everyone look over
> the release notes one last time:
> http://projects.scipy.org/scipy/numpy/milestone/1.1.0
> Please let me know if there are any important omissions or errors
> ASAP.
>
>
> Scalar indexing of matrices has changed, 1D arrays are now returned 
> instead of matrices. This has to be documented in the release notes.
>
> Chuck
>
>
> 
>
> ___
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>   

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

Hi Jarrod,

On Tue, May 6, 2008 at 2:40 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:

> Hey,
>
> The trunk is in pretty good shape and it is about time that I put out
> an official release.  So tomorrow (in a little over twelve hours) I am
> going to create a 1.1.x branch and the trunk will be officially open
> for 1.2 development.  If there are no major issues that show up at the
> last minute, I will tag 1.1.0 twenty-four hours after I branch.  As
> soon as I tag the release I will ask the David and Chris to create the
> official Windows and Mac binaries.  If nothing goes awry, you can
> expect the official release announcement by Monday, May 12th.
>
> In order to help me with the final touches, would everyone look over
> the release notes one last time:
> http://projects.scipy.org/scipy/numpy/milestone/1.1.0
> Please let me know if there are any important omissions or errors ASAP.
>

Scalar indexing of matrices has changed, 1D arrays are now returned instead
of matrices. This has to be documented in the release notes.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Wed, May 7, 2008 at 6:19 PM, Anne Archibald <[EMAIL PROTECTED]>
wrote:

> 2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
> >
> > On Wed, May 7, 2008 at 5:31 PM, Anne Archibald <
> [EMAIL PROTECTED]>
> > wrote:
> > > Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
> > > expect. Best not release without either backing out my change. I'm
> > > still trying to track down what's up.
> >
> > Returns a column matrix here, using  1.2.0.dev5143 after Travis's
> commits.
> > What should it do?
>
> Oh, uh, my bad. I messed up my test code, and panicked thinking Jarrod
> was about to release a borken 1.1.0 and it was going to be All My
> Fault.
>

I busted everything not so long ago by committing some borked files. I
couldn't find any easy way to revert the depository and fixing things up was
a pain.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
>
> Heh, I just added some tests to 1.2 before closing ticket #707. They  should
> probably be merged with yours.

Seems a shame:
Ran 1000 tests in 5.329s

Such a nice round number!

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Wed, May 7, 2008 at 6:17 PM, Anne Archibald <[EMAIL PROTECTED]>
wrote:

> 2008/5/7 Anne Archibald <[EMAIL PROTECTED]>:
> > 2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
> >
> >  > On Wed, May 7, 2008 at 11:44 AM, Anne Archibald <
> [EMAIL PROTECTED]>
> >  > wrote:
> >  > > 2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
> >  > >
> >  > > > I have just created the 1.1.x branch:
> >  > > >  http://projects.scipy.org/scipy/numpy/changeset/5134
> >  > > >  In about 24 hours I will tag the 1.1.0 release from the branch.
>  At
> >  > > >  this point only critical bug fixes should be applied to the
> branch.
> >  > > >  The trunk is now open for 1.2 development.
> >  > >
> >  > > I committed Travis' matrix indexing patch (plus a basic test) to
> >  > > 1.1.x. Hope that's okay. (All tests pass.)
> >  > >
> >  >
> >  > You should put it in the 1.2 branch also, then. I think fancy
> indexing and
> >  > tolist, which Travis mentioned as having matrix workarounds, need to
> be
> >  > checked to see if they still work correctly for matrices with the
> patch.
> >
> >  Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
> >  expect. Best not release without either backing out my change. I'm
> >  still trying to track down what's up.
>
> Okay, more tests committed. Travis has removed the .tolist()
> workaround (which, it turns out, doesn't actually depend on
> __getitem__). Not sure what needs to happen for fancy indexing -
> there's some alarming jiggery-pokery involving self._getitem that I
> don't understand. But these are not bugfixes anyway.


Heh, I just added some tests to 1.2 before closing ticket #707. They  should
probably be merged with yours.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
>
> On Wed, May 7, 2008 at 5:31 PM, Anne Archibald <[EMAIL PROTECTED]>
> wrote:
> > Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
> > expect. Best not release without either backing out my change. I'm
> > still trying to track down what's up.
>
> Returns a column matrix here, using  1.2.0.dev5143 after Travis's commits.
> What should it do?

Oh, uh, my bad. I messed up my test code, and panicked thinking Jarrod
was about to release a borken 1.1.0 and it was going to be All My
Fault.

That said, the only explicit test of .tolist() that I could find is
the one I just wrote...

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/7 Anne Archibald <[EMAIL PROTECTED]>:
> 2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
>
>  > On Wed, May 7, 2008 at 11:44 AM, Anne Archibald <[EMAIL PROTECTED]>
>  > wrote:
>  > > 2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
>  > >
>  > > > I have just created the 1.1.x branch:
>  > > >  http://projects.scipy.org/scipy/numpy/changeset/5134
>  > > >  In about 24 hours I will tag the 1.1.0 release from the branch.  At
>  > > >  this point only critical bug fixes should be applied to the branch.
>  > > >  The trunk is now open for 1.2 development.
>  > >
>  > > I committed Travis' matrix indexing patch (plus a basic test) to
>  > > 1.1.x. Hope that's okay. (All tests pass.)
>  > >
>  >
>  > You should put it in the 1.2 branch also, then. I think fancy indexing and
>  > tolist, which Travis mentioned as having matrix workarounds, need to be
>  > checked to see if they still work correctly for matrices with the patch.
>
>  Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
>  expect. Best not release without either backing out my change. I'm
>  still trying to track down what's up.

Okay, more tests committed. Travis has removed the .tolist()
workaround (which, it turns out, doesn't actually depend on
__getitem__). Not sure what needs to happen for fancy indexing -
there's some alarming jiggery-pokery involving self._getitem that I
don't understand. But these are not bugfixes anyway.

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Wed, May 7, 2008 at 5:31 PM, Anne Archibald <[EMAIL PROTECTED]>
wrote:

> 2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:
>
> > On Wed, May 7, 2008 at 11:44 AM, Anne Archibald <
> [EMAIL PROTECTED]>
> > wrote:
> > > 2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
> > >
> > > > I have just created the 1.1.x branch:
> > > >  http://projects.scipy.org/scipy/numpy/changeset/5134
> > > >  In about 24 hours I will tag the 1.1.0 release from the branch.  At
> > > >  this point only critical bug fixes should be applied to the branch.
> > > >  The trunk is now open for 1.2 development.
> > >
> > > I committed Travis' matrix indexing patch (plus a basic test) to
> > > 1.1.x. Hope that's okay. (All tests pass.)
> > >
> >
> > You should put it in the 1.2 branch also, then. I think fancy indexing
> and
> > tolist, which Travis mentioned as having matrix workarounds, need to be
> > checked to see if they still work correctly for matrices with the patch.
>
> Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
> expect. Best not release without either backing out my change. I'm
> still trying to track down what's up.


Returns a column matrix here, using  1.2.0.dev5143 after Travis's commits.
What should it do?

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/7 Charles R Harris <[EMAIL PROTECTED]>:

> On Wed, May 7, 2008 at 11:44 AM, Anne Archibald <[EMAIL PROTECTED]>
> wrote:
> > 2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
> >
> > > I have just created the 1.1.x branch:
> > >  http://projects.scipy.org/scipy/numpy/changeset/5134
> > >  In about 24 hours I will tag the 1.1.0 release from the branch.  At
> > >  this point only critical bug fixes should be applied to the branch.
> > >  The trunk is now open for 1.2 development.
> >
> > I committed Travis' matrix indexing patch (plus a basic test) to
> > 1.1.x. Hope that's okay. (All tests pass.)
> >
>
> You should put it in the 1.2 branch also, then. I think fancy indexing and
> tolist, which Travis mentioned as having matrix workarounds, need to be
> checked to see if they still work correctly for matrices with the patch.

Ah. Good point. I did find a bug - x[:,0] doesn't do what you'd
expect. Best not release without either backing out my change. I'm
still trying to track down what's up.

Guess our test suite leaves something to be desired.

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Wed, May 7, 2008 at 11:44 AM, Anne Archibald <[EMAIL PROTECTED]>
wrote:

> 2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
> > I have just created the 1.1.x branch:
> >  http://projects.scipy.org/scipy/numpy/changeset/5134
> >  In about 24 hours I will tag the 1.1.0 release from the branch.  At
> >  this point only critical bug fixes should be applied to the branch.
> >  The trunk is now open for 1.2 development.
>
> I committed Travis' matrix indexing patch (plus a basic test) to
> 1.1.x. Hope that's okay. (All tests pass.)
>

You should put it in the 1.2 branch also, then. I think fancy indexing and
tolist, which Travis mentioned as having matrix workarounds, need to be
checked to see if they still work correctly for matrices with the patch.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/7 Jarrod Millman <[EMAIL PROTECTED]>:
> I have just created the 1.1.x branch:
>  http://projects.scipy.org/scipy/numpy/changeset/5134
>  In about 24 hours I will tag the 1.1.0 release from the branch.  At
>  this point only critical bug fixes should be applied to the branch.
>  The trunk is now open for 1.2 development.

I committed Travis' matrix indexing patch (plus a basic test) to
1.1.x. Hope that's okay. (All tests pass.)

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Stéfan van der Walt]

2008/5/7 Albert Strasheim <[EMAIL PROTECTED]>:
>  Even better: let the Buildbot do it.
>
>  You should see some Valgrind output appearing in the testing output of
>  the Linux_x86_Fedora_Py2.6 builder soon. I'll probably have to tune
>  things a bit to make it go green/red in the right situations.

Fantastic -- that's really handy.  Thanks!

Cheers
Stéfan
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Albert Strasheim]

Hello,

On Wed, May 7, 2008 at 3:42 PM, Albert Strasheim <[EMAIL PROTECTED]> wrote:
>  Might be a bit late now, but are you (or is someone) still Valgrinding
>  NumPy on a semi-regular basis, or at least before a release?

Even better: let the Buildbot do it.

You should see some Valgrind output appearing in the testing output of
the Linux_x86_Fedora_Py2.6 builder soon. I'll probably have to tune
things a bit to make it go green/red in the right situations.

I'll also update the Linux_x86_64_Fedora builder later.

Regards,

Albert
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Albert Strasheim]

Hello,

On Wed, May 7, 2008 at 8:12 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> I have just created the 1.1.x branch:
>  http://projects.scipy.org/scipy/numpy/changeset/5134
>  In about 24 hours I will tag the 1.1.0 release from the branch.  At
>  this point only critical bug fixes should be applied to the branch.
>  The trunk is now open for 1.2 development.

Might be a bit late now, but are you (or is someone) still Valgrinding
NumPy on a semi-regular basis, or at least before a release?

Cheers,

Albert
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Jarrod Millman]

I have just created the 1.1.x branch:
http://projects.scipy.org/scipy/numpy/changeset/5134
In about 24 hours I will tag the 1.1.0 release from the branch.  At
this point only critical bug fixes should be applied to the branch.
The trunk is now open for 1.2 development.

Thanks,

-- 
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Bruce Southey]

Hi,
I think Ticket 605 (Incorrect behaviour of numpy.histogram) can be closed.

With regards to Ticket 706 (scalar indexing of matrices -> deprecation
warning) I think it should not be a blocker now but should apply the
next version. There were many different issues (and threads) raised in
the context of this often circular discussion. My conclusion was that
the Matrix class needs a clearer statement of the expected behavior
under different circumstances not just indexing.

I don't have Atlas installed to evaluate Ticket 551 and Ticket 748 is
outside my knowledge.

Regards
Bruce
.
On Tue, May 6, 2008 at 3:40 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Hey,
>
>  The trunk is in pretty good shape and it is about time that I put out
>  an official release.  So tomorrow (in a little over twelve hours) I am
>  going to create a 1.1.x branch and the trunk will be officially open
>  for 1.2 development.  If there are no major issues that show up at the
>  last minute, I will tag 1.1.0 twenty-four hours after I branch.  As
>  soon as I tag the release I will ask the David and Chris to create the
>  official Windows and Mac binaries.  If nothing goes awry, you can
>  expect the official release announcement by Monday, May 12th.
>
>  In order to help me with the final touches, would everyone look over
>  the release notes one last time:
>  http://projects.scipy.org/scipy/numpy/milestone/1.1.0
>  Please let me know if there are any important omissions or errors ASAP.
>
>  Also, there are four open tickets that I would like everyone to take a
>  brief look at:
>  http://projects.scipy.org/scipy/numpy/ticket/551
>  http://projects.scipy.org/scipy/numpy/ticket/605
>  http://projects.scipy.org/scipy/numpy/ticket/748
>  http://projects.scipy.org/scipy/numpy/ticket/760
>  I am not going to hold up the release any longer, but it would be nice
>  if a few (or all) of these remaining tickets could be closed.
>
>  Thanks,
>
>  --
>  Jarrod Millman
>  Computational Infrastructure for Research Labs
>  10 Giannini Hall, UC Berkeley
>  phone: 510.643.4014
>  http://cirl.berkeley.edu/
>  ___
>  Numpy-discussion mailing list
>  Numpy-discussion@scipy.org
>  http://projects.scipy.org/mailman/listinfo/numpy-discussion
>
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Anne Archibald]

2008/5/6 Charles R Harris <[EMAIL PROTECTED]>:
>
> On Tue, May 6, 2008 at 6:40 AM, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, 6 May 2008, Jarrod Millman apparently wrote:
> > > open tickets that I would like everyone to take a brief
> > > look at:
> > > http://projects.scipy.org/scipy/numpy/ticket/760
> >
> > My understanding is that my patch, which would give
> > a deprecation warning, was rejected in favor of the patch
> > specified at the end of Travis's message here:
> >
> http://projects.scipy.org/pipermail/numpy-discussion/2008-April/033315.html>
> >
> > At least that's how I thought things were resolved.
> > I expected Travis's patch would be part of the 1.1 release.
> >
>
> I think someone needs to step up and make the change, but first it needs to
> be blessed by Travis and some of the folks on the Matrix indexing thread.
> The change might also entail removing some workarounds in the spots
> indicated by Travis.

It has my vote, as a peripheral participant in the matrix indexing
thread; in fact it's what some of us thought we were agreeing to
earlier.

Anne
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Charles R Harris]

On Tue, May 6, 2008 at 6:40 AM, Alan G Isaac <[EMAIL PROTECTED]> wrote:

> On Tue, 6 May 2008, Jarrod Millman apparently wrote:
> > open tickets that I would like everyone to take a brief
> > look at:
> > http://projects.scipy.org/scipy/numpy/ticket/760
>
> My understanding is that my patch, which would give
> a deprecation warning, was rejected in favor of the patch
> specified at the end of Travis's message here:
>  http://projects.scipy.org/pipermail/numpy-discussion/2008-April/033315.html
> >
>
> At least that's how I thought things were resolved.
> I expected Travis's patch would be part of the 1.1 release.
>

I think someone needs to step up and make the change, but first it needs to
be blessed by Travis and some of the folks on the Matrix indexing thread.
The change might also entail removing some workarounds in the spots
indicated by Travis.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Status Report for NumPy 1.1.0

[Alan G Isaac]

On Tue, 6 May 2008, Jarrod Millman apparently wrote:
> open tickets that I would like everyone to take a brief 
> look at:
> http://projects.scipy.org/scipy/numpy/ticket/760 

My understanding is that my patch, which would give 
a deprecation warning, was rejected in favor of the patch
specified at the end of Travis's message here:
http://projects.scipy.org/pipermail/numpy-discussion/2008-April/033315.html>

At least that's how I thought things were resolved.
I expected Travis's patch would be part of the 1.1 release.

Cheers,
Alan



___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Status Report for NumPy 1.1.0

[Jarrod Millman]

Hey,

The trunk is in pretty good shape and it is about time that I put out
an official release.  So tomorrow (in a little over twelve hours) I am
going to create a 1.1.x branch and the trunk will be officially open
for 1.2 development.  If there are no major issues that show up at the
last minute, I will tag 1.1.0 twenty-four hours after I branch.  As
soon as I tag the release I will ask the David and Chris to create the
official Windows and Mac binaries.  If nothing goes awry, you can
expect the official release announcement by Monday, May 12th.

In order to help me with the final touches, would everyone look over
the release notes one last time:
http://projects.scipy.org/scipy/numpy/milestone/1.1.0
Please let me know if there are any important omissions or errors ASAP.

Also, there are four open tickets that I would like everyone to take a
brief look at:
http://projects.scipy.org/scipy/numpy/ticket/551
http://projects.scipy.org/scipy/numpy/ticket/605
http://projects.scipy.org/scipy/numpy/ticket/748
http://projects.scipy.org/scipy/numpy/ticket/760
I am not going to hold up the release any longer, but it would be nice
if a few (or all) of these remaining tickets could be closed.

Thanks,

-- 
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion