[Numpy-tickets] [NumPy] #558: 'axis' support for numpy.median()

[NumPy]

#558: 'axis' support for numpy.median()
-------------------------+--------------------------------------------------
 Reporter:  cdavid       |        Owner:  somebody
     Type:  enhancement  |       Status:  new     
 Priority:  normal       |    Milestone:  1.0.5   
Component:  numpy.core   |      Version:  devel   
 Severity:  normal       |   Resolution:          
 Keywords:               |  
-------------------------+--------------------------------------------------
Changes (by jarrod.millman):

  * version:  none => devel
  * component:  Other => numpy.core
  * milestone:  1.1 => 1.0.5

Comment:

 On 30 Jan 2008, at 00:32, Travis E. Oliphant wrote:
 > I'm fine with a median API change for 1.1.
 >
 > We can add the axis keyword for 1.0.5 as long as the default stays
 > the same.  We can also add the other keywords as well if appropriate
 > defaults can be determined.
 >
 > -Travis O.

 Joris De Ridder wrote:
 > Do you mean creating a median(a, axis=0) for 1.0.5, and changing it to
 > median(a,axis=None) for 1.1? (Modulo other keywords).
 >
 > Joris

 On Jan 29, 2008 5:48 PM, Travis E. Oliphant <oliphant@enthought.com>
 wrote:
 > Yes.   That is the approach I prefer.
 >
 > -Travis

 Timothy Hochberg wrote:
 > I'm all for fixing this, but the prospect of going straight from  one
 > default to another makes me nervous. Is there is any prospect we could
 > spit out a warning when an axis is not specified for median starting
 > in 1.05 up till 1.1. It could even be a !PendingDeprecationWarning,
 > which by default doesn't print anything I believe, but would allow
 > people to check there code for potential failure points.

 On Jan 30, 2008 10:41 AM, Travis E. Oliphant <oliphant@enthought.com>
 wrote:
 > Yes, we could start to do that (spit out a warning in 1.0.5).  This
 > should definitely be done in 1.0.6
 >
 > Perhaps we use axis=None to start with and then check for that and spit
 > out the warning (and change axis to 0). Thanks for the pointer to
 > !PendingDeprecationWarning.
 >
 > We could also have an APIChangeWarning that we define in !NumPy which
 > would allow !SciPy to use it as well.

 from http://projects.scipy.org/pipermail/numpy-
 discussion/2008-January/031053.html

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