On Sun, May 30, 2010 at 5:53 PM, Ralf Gommers <ralf.gomm...@googlemail.com>wrote:
> > > On Mon, May 31, 2010 at 2:06 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sun, May 30, 2010 at 9:52 AM, Ralf Gommers < >> ralf.gomm...@googlemail.com> wrote: >> >>> >>> >>> On Sat, May 29, 2010 at 9:05 AM, Pauli Virtanen <p...@iki.fi> wrote: >>> >>>> Fri, 28 May 2010 12:13:57 -0500, Travis Oliphant wrote: >>>> [clip] >>>> > I think this makes sense so that we can reschedule NumPy 2.0 for >>>> > September and still provide a release with the Python 3k changes (I am >>>> > assuming these can be done in an ABI-compatible way). >>>> >>>> As far as I remember, the Py3 changes did not require breaking ABI (on >>>> Py2). >>>> >>>> Good. How much work is it to remove datetime, and who wants to do it? >>> >>> >> Hey, I thought that was your job ;) Maybe the best thing is to start by >> making a branch for the removal and we can argue about who gets the short >> end of the stick later... >> >> Manage the release yes, do the heavy lifting not necessarily:) OK, I'll > make the branch tonight. > > If the removal just involves the same changes that were made for 1.4.1 then > I can do it. But I'm not familiar with this code and if it's more work, I > probably won't have time for it between the scipy 0.8.0 release and my 'real > job', like you call it. > > I think it may be a bit trickier because Travis made more changes. I think the relevant commits are r8113..r8115 and 8107..8108. After removing those we still need to remove the same stuff as we did for the 1.4.1 release. We will need some way of testing if the removal was successful. We probably want to make sure there is a documentation update also, maybe before making the branch. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
