I've made a PR for this. The commit message is
Deal with subclasses of ndarray, like pandas.Series and matrix.
Subclasses may not define the new keyword keepdims or deal
gracefully with ufuncs in all their forms. This is solved by
throwing the problem onto the np.sum,
Hello,
sorry, I don't know where exactly jump in in the thread, it is getting
quite long and articulated...
On 02/10/2013 21:19, Charles R Harris wrote:
The main problem I had was deciding what arg{max, min} should return as
the return value is an integer. I like your suggestion of returning
On 03/10/2013 13:56, Charles R Harris wrote:
On Thu, Oct 3, 2013 at 4:06 AM, Daniele Nicolodi dani...@grinta.net
mailto:dani...@grinta.net wrote:
Hello,
sorry, I don't know where exactly jump in in the thread, it is getting
quite long and articulated...
On 02/10/2013
On Thu, Oct 3, 2013 at 6:06 AM, Daniele Nicolodi dani...@grinta.net wrote:
Hello,
sorry, I don't know where exactly jump in in the thread, it is getting
quite long and articulated...
On 02/10/2013 21:19, Charles R Harris wrote:
The main problem I had was deciding what arg{max, min} should
On Thu, Oct 3, 2013 at 9:10 AM, Benjamin Root ben.r...@ou.edu wrote:
On Thu, Oct 3, 2013 at 6:06 AM, Daniele Nicolodi dani...@grinta.net wrote:
Hello,
sorry, I don't know where exactly jump in in the thread, it is getting
quite long and articulated...
On 02/10/2013 21:19, Charles R Harris
snip
Please, no. It's another thing to remember and another way to shoot
yourself in the foot and introduce casual bugs.
FWIW, my vote is to raise an error or return a nan, which will likely
eventually raise an error. If I have all nans, it's usually the case
that something's off, and I'd
On Thu, Oct 3, 2013 at 7:59 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
snip
Please, no. It's another thing to remember and another way to shoot
yourself in the foot and introduce casual bugs.
FWIW, my vote is to raise an error or return a nan, which will likely
eventually raise
On Thu, Oct 3, 2013 at 1:11 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Oct 3, 2013 at 7:59 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
snip
Please, no. It's another thing to remember and another way to shoot
yourself in the foot and introduce casual bugs.
FWIW,
On 03/10/2013 20:59, Charles R Harris wrote:
Here is what I have currently implemented. First, define an AllNanError
class AllNanError(ValueError):
def __init__(self, msg, result):
ValueError.__init__(self, msg)
self.result = result
For
On Thu, Oct 3, 2013 at 8:40 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Thu, Oct 3, 2013 at 1:11 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Oct 3, 2013 at 7:59 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
snip
Please, no. It's another thing to remember
Hi All,
The question is what to do when all-nan slices are encountered in the
nan{max,min} and nanarg{max, min} functions. Currently in 1.8.0, the first
returns nan and raises a warning, the second returns intp.min and raises a
warning. It is proposed that the nanarg{max, min} functions, and
+1 to making the nan functions consistent with the non-nan functions.
On 2 Oct 2013 17:03, Charles R Harris charlesr.har...@gmail.com wrote:
Hi All,
The question is what to do when all-nan slices are encountered in the
nan{max,min} and nanarg{max, min} functions. Currently in 1.8.0, the first
On 2 Oct 2013 18:04, Charles R Harris charlesr.har...@gmail.com wrote:
The question is what to do when all-nan slices are encountered in the
nan{max,min} and nanarg{max, min} functions. Currently in 1.8.0, the first
returns nan and raises a warning, the second returns intp.min and raises a
On Wed, Oct 2, 2013 at 12:37 PM, Stéfan van der Walt ste...@sun.ac.za wrote:
On 2 Oct 2013 18:04, Charles R Harris charlesr.har...@gmail.com wrote:
The question is what to do when all-nan slices are encountered in the
nan{max,min} and nanarg{max, min} functions. Currently in 1.8.0, the first
On Wed, Oct 2, 2013 at 10:56 AM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 12:37 PM, Stéfan van der Walt ste...@sun.ac.za
wrote:
On 2 Oct 2013 18:04, Charles R Harris charlesr.har...@gmail.com
wrote:
The question is what to do when all-nan slices are encountered in the
On Wed, Oct 2, 2013 at 1:05 PM, Charles R Harris
charlesr.har...@gmail.comwrote:
On Wed, Oct 2, 2013 at 10:56 AM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 12:37 PM, Stéfan van der Walt ste...@sun.ac.za
wrote:
On 2 Oct 2013 18:04, Charles R Harris charlesr.har...@gmail.com
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent, I think. a[nanargmax(a)] == nanmax(a)
(ignoring the silly detail that you can't do an equality on nans).
Why do you call this a silly detail? It seems to me a fundamental flaw to
this approach.
Stéfan
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.za wrote:
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent, I think. a[nanargmax(a)] == nanmax(a)
(ignoring the silly detail that you can't do an equality on nans).
Why do you call this
On Wed, Oct 2, 2013 at 2:49 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.za wrote:
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent, I think. a[nanargmax(a)] == nanmax(a)
(ignoring the silly detail
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.zawrote:
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent, I think. a[nanargmax(a)] == nanmax(a)
(ignoring the silly detail that you can't do an equality on nans).
Why do you call
On Wed, Oct 2, 2013 at 7:51 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:49 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.za wrote:
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent, I
On Wed, Oct 2, 2013 at 12:51 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:49 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.za
wrote:
On 2 Oct 2013 19:14, Benjamin Root ben.r...@ou.edu wrote:
And it is logically consistent,
On Wed, Oct 2, 2013 at 8:19 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Wed, Oct 2, 2013 at 12:51 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:49 PM, josef.p...@gmail.com wrote:
On Wed, Oct 2, 2013 at 2:05 PM, Stéfan van der Walt ste...@sun.ac.za
wrote:
On 2
On 2 Oct 2013 21:19, Charles R Harris charlesr.har...@gmail.com wrote:
The main problem I had was deciding what arg{max, min} should return as
the return value is an integer. I like your suggestion of returning 0.
This doesn't allow the user to know the difference between valid and
invalid
24 matches
Mail list logo
