Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-28 Thread Mark Wiebe
On Fri, Jan 28, 2011 at 4:14 PM, Charles R Harris wrote: > > > Go ahead and merge it in and we'll see how it goes. > > I did the merge, and tried to trigger the buildbot, but it looks like a github svn issue has reared its head: http://support.github.com/discussions/repos/3155-svn-checkout-erro

Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-28 Thread Charles R Harris
On Fri, Jan 28, 2011 at 4:37 PM, Mark Wiebe wrote: > Does anyone have any objections to me merging the branch into the numpy > trunk right now? > > Chuck suggested I try to split out the ABI changes, but they're kind of > tangled with the other changes. In particular, they involve fixing the typ

Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-28 Thread Mark Wiebe
Does anyone have any objections to me merging the branch into the numpy trunk right now? Chuck suggested I try to split out the ABI changes, but they're kind of tangled with the other changes. In particular, they involve fixing the type promotion code to be enum order-independent, which depended

Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-28 Thread Bruce Southey
On 01/27/2011 10:58 PM, David Cournapeau wrote: > On Fri, Jan 28, 2011 at 12:46 PM, Charles R Harris > wrote: >> Hi All, >> >> Mark Wiebe has proposed making the master branch backward compatible with >> 1.5. The argument for doing this is that 1) removing the new bits for new >> releases is a ch

Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-28 Thread Pauli Virtanen
Thu, 27 Jan 2011 20:46:22 -0700, Charles R Harris wrote: > Mark Wiebe has proposed making the master branch backward compatible > with 1.5. The argument for doing this is that 1) removing the new bits > for new releases is a chore as the refactor schedule slips and 2) the > new ABI isn't settled an

Re: [Numpy-discussion] Should we make the master branch backward compatible.

2011-01-27 Thread David Cournapeau
On Fri, Jan 28, 2011 at 12:46 PM, Charles R Harris wrote: > Hi All, > > Mark Wiebe has proposed making the master branch backward compatible with > 1.5. The argument for doing this is that 1) removing the new bits for new > releases is a chore as the refactor schedule slips and 2) the new ABI isn'

[Numpy-discussion] Should we make the master branch backward compatible.

2011-01-27 Thread Charles R Harris
Hi All, Mark Wiebe has proposed making the master branch backward compatible with 1.5. The argument for doing this is that 1) removing the new bits for new releases is a chore as the refactor schedule slips and 2) the new ABI isn't settled and keeping the current code in won't help with the merge.