[Numpy-tickets] [NumPy] #661: maximum handles nan improperly

[NumPy]

#661: maximum handles nan improperly
--------------------+-------------------------------------------------------
 Reporter:  tmb     |        Owner:  somebody
     Type:  defect  |       Status:  closed  
 Priority:  normal  |    Milestone:  1.0.5   
Component:  Other   |      Version:  none    
 Severity:  normal  |   Resolution:  wontfix 
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by rkern):

  * status:  reopened => closed
  * resolution:  => wontfix

Comment:

 If you wish to dispute/discuss a ticket after it has been closed by a
 developer, the mailing list is the place to do it, not the ticket.

 Please take a look at what setting {{{invalid='warn'}}} actually does. The
 behavior you are seeing is actually {{{invalid='print'}}}. Personally, I
 would like {{{invalid='warn'}}} to be the default, too. Changing that
 default would probably be okay to do at this point in time, but it would
 take a certain amount of deliberation. Using the Python warnings system is
 not without costs.

 If you wish clearer documentation, please provide some. Now that you know
 about seterr(), you know better than I do what would have helped you find
 seterr(). Note that we can't practically modify the docstrings of all of
 the functions affected by seterr() since almost every single function is
 affected.

 There is little (defined) relationship between seterr() and fpectl because
 fpectl is no longer supported by the Python team.

-- 
Ticket URL: <http://www.scipy.org/scipy/numpy/ticket/661#comment:3>
NumPy <http://projects.scipy.org/scipy/numpy>
The fundamental package needed for scientific computing with Python.