On Sun, Mar 25, 2012 at 6:48 PM, Charles R Harris <charlesr.har...@gmail.com > wrote:
> > > On Sun, Mar 25, 2012 at 10:33 AM, Ralf Gommers < > ralf.gomm...@googlemail.com> wrote: > >> >> >> On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris < >> charlesr.har...@gmail.com> 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 >>> outstanding. >>> >> There's one more ticket that hasn't been looked at AFAIK and that has >> been keeping the buildbots (except the Linux one) on red: >> http://projects.scipy.org/numpy/ticket/1755 (floating point errors). >> >> > I don't know what to do about that one.There may be some compiler flags > that would help. > Why do you think this isn't a problem with the implementation? I haven't tried to look at this in detail, but Python itself does manage to produce a warning: >>> 2.0**2048 Traceback (most recent call last): File "<stdin>", line 1, in <module> OverflowError: (34, 'Result too large') >>> import numpy as np >>> np.power(2.0, 2048) inf >>> np.geterr() {'over': 'warn', 'divide': 'warn', 'invalid': 'warn', 'under': 'ignore'} Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
