On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers <ralf.gomm...@googlemail.com> wrote: > > > On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant <tra...@continuum.io> > 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 July 18th (7:00pm CDT on >> July 17th). This will allow the creation of beta releases of NumPy on the >> 18th of July. This is a few days later than originally hoped for --- largely >> due to unexpected travel schedules of Ondrej and I, but it does give people >> a few more days to get patches in. Of course, we will be able to apply >> bug-fixes to the 1.7.x branch once the tag is made. > > > 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
Is there a description anywhere of what the problem actually is here? I looked at the ticket, which referred to a PR, and it's hard to work out from the PR discussion what the actual remaining test failures are -- and there definitely doesn't seem to be any description of the underlying problem. (Something about working 64-bit time_t on windows being difficult depending on the compiler used?) > - #2076 Bus error for F order ndarray creation on SPARC Yes, this looks like a regression... Mark, any thoughts? > These have patches available which should be reviewed: > - #2150 Distutils should support Debian multi-arch fully This PR still needs tests and has unresolved comments, but is probably a blocker: https://github.com/numpy/numpy/pull/327 -N _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
