Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-16 Thread Russell E. Owen
In article <1342393528.28368.3.ca...@esdceeprjpstudent1.mit.edu>, Paul Natsuo Kishimoto wrote: > On Sat, 2012-07-14 at 17:45 -0500, Travis Oliphant wrote: > > Hey all, > > > > We are nearing a code-freeze for NumPy 1.7. Are there any > > last-minute changes people are wanting to push into Nu

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-16 Thread Nathaniel Smith
On Mon, Jul 16, 2012 at 3:52 AM, Frédéric Bastien wrote: > Hi, > > there is a PR that I think could be merged before the relase: > > https://github.com/numpy/numpy/pull/326 > > It is the addition of the inplace_increment function. It seam good, > but I can't review it enough as it use many numpy i

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Ralf Gommers
On Mon, Jul 16, 2012 at 2:01 AM, Travis Oliphant wrote: > > On Jul 15, 2012, at 7:08 AM, Ralf Gommers wrote: > > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant wrote: > >> >> Hey all, >> >> We are nearing a code-freeze for NumPy 1.7. Are there any last-minute >> changes people are wanting

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Travis Oliphant
This looked like an interesting one for sure. I can't look at the PR right now for some reason (Github gave me a 500 error). I know there were some comments, though. -Travis On Jul 15, 2012, at 9:52 PM, Frédéric Bastien wrote: > Hi, > > there is a PR that I think could be merged before

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Frédéric Bastien
Hi, there is a PR that I think could be merged before the relase: https://github.com/numpy/numpy/pull/326 It is the addition of the inplace_increment function. It seam good, but I can't review it enough as it use many numpy internal that I never used or looked at. But the tests seam to cover all

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Travis Oliphant
> > Bump for: https://github.com/numpy/numpy/pull/351 > > > As requested by njsmith, I gave a more detailed explanation and asked > the list for input at: > http://www.mail-archive.com/numpy-discussion@scipy.org/msg38306.html > > There was one qualified negative reply and nothing (yet) further.

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Travis Oliphant
On Jul 15, 2012, at 7:08 AM, Ralf Gommers wrote: > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant wrote: > > Hey all, > > We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > changes people are wanting to push into NumPy 1.7? We should discuss them as > soon as

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Paul Natsuo Kishimoto
On Sat, 2012-07-14 at 17:45 -0500, Travis Oliphant wrote: > Hey all, > > We are nearing a code-freeze for NumPy 1.7. Are there any > last-minute changes people are wanting to push into NumPy 1.7? We > should discuss them as soon as possible. > > I'm proposing a code-freeze at midnight UTC on

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread jay bourque
Just added PR #359. The purpose is to allow the nditer object operand and iter flags to be set for a ufunc to provide better control over how an array is iterated over by a ufunc and how the ufunc uses the operands passed to it. One specific motivation for this is to be able to specify an input ope

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Charles R Harris
On Sun, Jul 15, 2012 at 10:56 AM, David Cournapeau wrote: > On Sun, Jul 15, 2012 at 5:42 PM, Charles R Harris > wrote: > > > > > > On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers < > ralf.gomm...@googlemail.com> > > wrote: > >> > >> > >> > >> On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith wrote

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Stefan Krah
Nathaniel Smith wrote: > > What about the tickets still open for 1.7.0 > > (http://projects.scipy.org/numpy/report/3)? There are a few important ones > > left. > > > > These I would consider blockers: > > - #2108 Datetime failures with MinGW I wonder if this might be a blocker: Python-3.3 will

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread David Cournapeau
On Sun, Jul 15, 2012 at 5:42 PM, Charles R Harris wrote: > > > On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers > wrote: >> >> >> >> On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith wrote: >>> >>> On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers >>> wrote: >>> > >>> > >>> > On Sun, Jul 15, 2012 at 1

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Charles R Harris
On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers wrote: > > > On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith wrote: > >> On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers >> wrote: >> > >> > >> > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant >> > wrote: >> >> >> >> >> >> Hey all, >> >> >> >> We

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Ralf Gommers
On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith wrote: > On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers > wrote: > > > > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant > > wrote: > >> > >> > >> Hey all, > >> > >> We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > >

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Nathaniel Smith
On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers wrote: > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant > wrote: >> >> >> Hey all, >> >> We are nearing a code-freeze for NumPy 1.7. Are there any last-minute >> changes people are wanting to push into NumPy 1.7? We should discuss them >> as

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Ralf Gommers
On Sun, Jul 15, 2012 at 5:33 PM, Thouis (Ray) Jones wrote: > > On Jul 15, 2012 2:08 PM, "Ralf Gommers" > wrote: > > > > > > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant > wrote: > >> > >> > >> Hey all, > >> > >> We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > c

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Thouis (Ray) Jones
On Jul 15, 2012 2:08 PM, "Ralf Gommers" wrote: > > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant wrote: >> >> >> Hey all, >> >> We are nearing a code-freeze for NumPy 1.7. Are there any last-minute changes people are wanting to push into NumPy 1.7? We should discuss them as soon as pos

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-15 Thread Ralf Gommers
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant wrote: > > Hey all, > > We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > changes people are wanting to push into NumPy 1.7? We should discuss them > as soon as possible. > > I'm proposing a code-freeze at midnight UTC on J

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-14 Thread Charles R Harris
On Sat, Jul 14, 2012 at 7:02 PM, Matthew Brett wrote: > Hi, > > On Sat, Jul 14, 2012 at 3:45 PM, Travis Oliphant > wrote: > > > > Hey all, > > > > We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > changes people are wanting to push into NumPy 1.7? We should discuss them >

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-14 Thread Matthew Brett
Hi, On Sat, Jul 14, 2012 at 3:45 PM, Travis Oliphant wrote: > > Hey all, > > We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > changes people are wanting to push into NumPy 1.7? We should discuss them as > soon as possible. > > I'm proposing a code-freeze at midnight UT

Re: [Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-14 Thread Frédéric Bastien
A very small PR about documentation: https://github.com/numpy/numpy/pull/332 Fred On Sat, Jul 14, 2012 at 6:45 PM, Travis Oliphant wrote: > > Hey all, > > We are nearing a code-freeze for NumPy 1.7. Are there any last-minute > changes people are wanting to push into NumPy 1.7? We should dis

[Numpy-discussion] Code Freeze for NumPy 1.7

2012-07-14 Thread Travis Oliphant
Hey all, We are nearing a code-freeze for NumPy 1.7. Are there any last-minute changes people are wanting to push into NumPy 1.7? We should discuss them as soon as possible. I'm proposing a code-freeze at midnight UTC on July 18th (7:00pm CDT on July 17th). This will allow the creation