On Sun, Mar 7, 2010 at 4:41 AM, Friedrich Romstedt < friedrichromst...@gmail.com> wrote:
> 2010/3/5 Pierre GM <pgmdevl...@gmail.com>: > > 'm'fraid no. I gonna have to investigate that. Please open a ticket with > a self-contained example that reproduces the issue. > > Thx in advance... > > P. > > I would like to stress the fact that imo this is maybe not ticket and not a > bug. > > The issue arises when calling a.max() or similar of empty arrays a, i.e., > with: > > >>> 0 in a.shape > True > > Opposed to the .prod() of an empty array, such a .max() or .min() > cannot be defined, because the set is empty. So it's fully correct to > let such calls fail. Just the failure is a bit deep in numpy, and > only the traceback gives some hint what went wrong. > > I posted something similar also on the matplotlib-users list, sorry > for cross-posting thus. > Any suggestions, then, how to go about figuring out what's happening in my code that's causing this "feature" to manifest itself? DG > > fwiw, > Friedrich > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
