[Numpy-discussion] 1.7 blockers
Tue Mar 27 15:19:02 CDT 2012
On Mon, Mar 26, 2012 at 1:27 AM, Charles R Harris <firstname.lastname@example.org
> On Sun, Mar 25, 2012 at 3:14 PM, Ralf Gommers <email@example.com
> > wrote:
>> On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris <
>> firstname.lastname@example.org> wrote:
>>> Hi All,
>>> There several problems with numpy master that need to be fixed before a
>>> release can be considered.
>>> 1. Datetime on windows with mingw.
>>> 2. Bus error on SPARC, ticket #2076.
>>> 3. NA and real/complex views of complex arrays.
>>> Number 1 has been proved to be particularly difficult, any help or
>>> suggestions for that would be much appreciated. The current work has been
>>> going in pull request 214 <https://github.com/numpy/numpy/pull/214>.
>>> This isn't to say that there aren't a ton of other things that need
>>> fixing or that we can skip out on the current stack of pull requests, but I
>>> think it is impossible to consider a release while those three problems are
>> Why do you consider (2) a blocker? Not saying it's not important, but
>> there are eight other open tickets with segfaults. Some are more esoteric
>> than other, but I don't see why for example #1713 and #1808 are less
>> important than this one.
>> #1522 provides a patch that fixes a segfault by the way, could use a
> I wasn't aware of the other segfaults, I'd like to get them all fixed...
> The list was meant to elicit additions.
> There are actually even more, I just searched for "segfault" to find the
8. Search for "segmentation fault" or "bus error" in Trac.
I would hope these have a high priority to get fixed but, unless they're
backwards compatibility issues, I don't consider them blockers. For the
simple reason that then we'd never be able to ship any release.
I don't know where the missed floating point errors come from, but they are
> somewhat dependent on the compiler doing the right thing and hardware
> support. I'd welcome any insight into why we get them on SPARC (underflow)
> and Windows (overflow).
> The windows buildbot doesn't seem to be updating correctly since it is
> still missing the combinations method that is now part of the test module.
Yeah, none of them are updating, it's a pain. We'll hopefully soon be able
to switch to a shiny new one.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion