Right.
On Thu, Apr 16, 2015 at 6:44 PM, Nathaniel Smith wrote:
> On Thu, Apr 16, 2015 at 6:37 PM, Neil Girdhar
> wrote:
> > I can always put np.outer = np.multiply.outer at the start of my code to
> get
> > what I want. Or could that break things?
>
> Please don't do this. It means that there
On Thu, Apr 16, 2015 at 6:37 PM, Neil Girdhar wrote:
> I can always put np.outer = np.multiply.outer at the start of my code to get
> what I want. Or could that break things?
Please don't do this. It means that there are any calls to np.outer in
libraries you are using (or other libraries that a
On Thu, Apr 16, 2015 at 6:32 PM, Nathaniel Smith wrote:
> On Thu, Apr 16, 2015 at 6:19 PM, Neil Girdhar
> wrote:
> > Actually, looking at the docs, numpy.outer is *only* defined for 1-d
> > vectors. Should anyone who used it with multi-dimensional arrays have an
> > expectation that it will kee
That sounds good to me.
I can always put np.outer = np.multiply.outer at the start of my code to
get what I want. Or could that break things?
On Thu, Apr 16, 2015 at 6:28 PM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Apr 16, 2015 at 3:19 PM, Neil Girdhar
> wrote:
> > Actually, looking at the doc
On Thu, Apr 16, 2015 at 6:19 PM, Neil Girdhar wrote:
> Actually, looking at the docs, numpy.outer is *only* defined for 1-d
> vectors. Should anyone who used it with multi-dimensional arrays have an
> expectation that it will keep working in the same way?
Yes. Generally what we do is more import
Hi,
On Thu, Apr 16, 2015 at 3:19 PM, Neil Girdhar wrote:
> Actually, looking at the docs, numpy.outer is *only* defined for 1-d
> vectors. Should anyone who used it with multi-dimensional arrays have an
> expectation that it will keep working in the same way?
>
> On Thu, Apr 16, 2015 at 10:53 AM
Actually, looking at the docs, numpy.outer is *only* defined for 1-d
vectors. Should anyone who used it with multi-dimensional arrays have an
expectation that it will keep working in the same way?
On Thu, Apr 16, 2015 at 10:53 AM, Neil Girdhar
wrote:
> Would it be possible to deprecate np.outer
Would it be possible to deprecate np.outer's usage on non one-dimensional
vectors for a few versions, and then reintroduce it with definition
np.outer == np.multiply.outer?
On Wed, Apr 15, 2015 at 8:02 PM, wrote:
> On Wed, Apr 15, 2015 at 6:40 PM, Nathaniel Smith wrote:
> > On Wed, Apr 15, 2015
