It was not clear. Here is the new version:

Make many reduction functions accept a numpy scalar as axis (Jeremiah Lowin)

We where supporting python int, but not numpy scalar (I don,t remember if
we support numpy.ndarray, that is not the same)

Is that sentence more clear?



On Tue, Nov 19, 2013 at 4:47 PM, David Warde-Farley <
notifications@github.com> wrote:

> In NEWS_DEV.txt:
>
> > @@ -88,6 +153,10 @@ New Features:
> >   * Make GpuCrossentropySoftmaxArgmax1HotWithBias and GpuCrossentropySoftmax1HotWithBiasDx work for bigger inputs (Frederic B., reported by Ryan Price)
> >   * Finish and move out of sandbox theano.sparse.basic.true_dot (Nicolas Bouchard, Frederic B.)
> >     And document all sparse dot variants.
> > + * Implement the mode ignore_borders for GpuImages2Neibs (Frederic B.)
> > + * Make many reduction algo accept a scalar numpy.ndarray as axis (Jeremiah Lowin)
>
> I thought this was already in. Did you mean that Jeremiah added support
> for multiple axes? I thought that was the new thing.
>
> If this is true, I would describe it as
>
> "Added support for a 1-d numpy.ndarray in place of a scalar for specifying
> multiple axes in many reduction operations."
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Theano/Theano/pull/1611/files#r7773908>
> .
>