If there is support, then it will appear in the new RandomGenerator, but
> not the RandomState replacement. If not, then we can just delete it.
>
>
+1 for complex normal generation.
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mai
+1 for keeping the same CoC as Scipy, making a new thing just seems a
bigger surface area to maintain. Personally I already assumed Scipy's
"honour[ing] diversity in..." did not imply any protection of
behaviours that violate the CoC *itself*, but if you wanted to be
really explicit you could add "
> Date: Fri, 19 Jan 2018 23:55:57 +0900
> From: Robert Kern
>
> tl;dr: I think that our stream-compatibility policy is holding us back, and
> I think we can come up with a way forward with a new policy that will allow
> us to innovate without seriously compromising our reliability.
>
> I propose t
> Date: Fri, 27 Oct 2017 17:52:23 -0400
> From: Marten van Kerkwijk
>
> Hi Peter,
>
> When using units, if `a` is not angular (or dimensionless), I don't
> see how one could write code in which your example wouldn't fail...
> But I may be missing something, since for your example one would just
> r
> Date: Thu, 26 Oct 2017 17:27:33 -0400
> From: Marten van Kerkwijk
>
> That sounds somewhat puzzling as units cannot really propagate without
> them somehow telling how they would change! (e.g., the outcome of
> sin(a) is possible only for angular units and then depends on that
> unit). But in any
> > On Thu, Oct 26, 2017 at 12:11 PM, Daniele Nicolodi
> > wrote:
> >
> >> is there a better way to write the dot product between a stack of
> >> matrices? In my case I need to compute
> >>
> >> y = A.T @ inv(B) @ A
> >>
> >> with A a 3x1 matrix and B a 3x3 matrix, N times, with N in the few
> >>
e
sausage-machine of scipy.spatial.cKDTree.query (to find distances to
neighbours) and my units are toast.
That probably sounds stronger than I meant - keeping track of units
systematically is neither easy nor unimportant and I have enormous
respect for the developers of Astropy and the community they have
bui
> From: Stephan Hoyer
>
> I like the idea of a strategy keyword argument. strategy='auto' leaves the
> door open for future improvements, e.g., if we ever add hash tables to
> numpy.
>
> For the algorithm, I think we actually want to sort the needles array as
> well in most (all?) cases.
>
> If ha
